diff options
author | Fabricio Voznika <fvoznika@google.com> | 2019-10-16 14:33:23 -0700 |
---|---|---|
committer | gVisor bot <gvisor-bot@google.com> | 2019-10-16 15:06:24 -0700 |
commit | 9fb562234e7858dbc60e8771f851629464edf205 (patch) | |
tree | 81249d5366078261dd759a34b9d42dd22ab6f140 /pkg/flipcall/flipcall_unsafe.go | |
parent | fd4e43600242c4929269afd529a8c1de4681e62e (diff) |
Fix problem with open FD when copy up is triggered in overlayfs
Linux kernel before 4.19 doesn't implement a feature that updates
open FD after a file is open for write (and is copied to the upper
layer). Already open FD will continue to read the old file content
until they are reopened. This is especially problematic for gVisor
because it caches open files.
Flag was added to force readonly files to be reopenned when the
same file is open for write. This is only needed if using kernels
prior to 4.19.
Closes #1006
It's difficult to really test this because we never run on tests
on older kernels. I'm adding a test in GKE which uses kernels
with the overlayfs problem for 1.14 and lower.
PiperOrigin-RevId: 275115289
Diffstat (limited to 'pkg/flipcall/flipcall_unsafe.go')
0 files changed, 0 insertions, 0 deletions