summaryrefslogtreecommitdiffhomepage
path: root/pkg/sentry/kernel/signalfd
diff options
context:
space:
mode:
authorNicolas Lacasse <nlacasse@google.com>2019-09-30 13:06:27 -0700
committergVisor bot <gvisor-bot@google.com>2019-09-30 13:08:45 -0700
commit3ad17ff5977bc639418f5409396fac8b3ceb370b (patch)
treee1ec4a50e7eec972e1d3dc427809c7784917a374 /pkg/sentry/kernel/signalfd
parent981fc188f0f0250ad59e39d566a56c71430b3287 (diff)
Force timestamps to update when set via InodeOperations.SetTimestamps.
The gofer's CachingInodeOperations implementation contains an optimization for the common open-read-close pattern when we have a host FD. In this case, the host kernel will update the timestamp for us to a reasonably close time, so we don't need an extra RPC to the gofer. However, when the app explicitly sets the timestamps (via futimes or similar) then we actually DO need to update the timestamps, because the host kernel won't do it for us. To fix this, a new boolean `forceSetTimestamps` was added to CachineInodeOperations.SetMaskedAttributes. It is only set by gofer.InodeOperations.SetTimestamps. PiperOrigin-RevId: 272048146
Diffstat (limited to 'pkg/sentry/kernel/signalfd')
0 files changed, 0 insertions, 0 deletions