summaryrefslogtreecommitdiffhomepage
path: root/pkg/lisafs/sock.go
diff options
context:
space:
mode:
authorJamie Liu <jamieliu@google.com>2021-10-12 10:23:01 -0700
committergVisor bot <gvisor-bot@google.com>2021-10-12 10:25:30 -0700
commit8682ce689e928ec32ec810a7eb038fb582c66093 (patch)
tree055b5c20bf179fe839ac6da0ceb434c7effbc512 /pkg/lisafs/sock.go
parentab1ef0baba1d15c4d4e7717d23cf8b32fd6b5feb (diff)
Remove state:"nosave"/"zerovalue" annotations from all waiter.Queues.
Prior to cl/318010298, //pkg/state couldn't handle pointers to struct fields, which meant that it couldn't handle intrusive linked lists, which meant that it couldn't handle waiter.Queue, which meant that it couldn't handle epoll. As a result, VFS1 unregisters all epoll waiters before saving and re-registers them after loading, and waitable VFS1 file implementations tag their waiter.Queues state:"nosave" (causing them to be skipped by the save/restore machinery) or state:"zerovalue" (causing them to only be checked for zero-value-equality on save). VFS2 required cl/318010298 to support save/restore (due to the Impl inheritance pattern used by vfs.FileDescription, vfs.Dentry, etc.); correspondingly, VFS2 epoll assumes that waiter.Queues *will be* saved and loaded correctly, and VFS2 file implementations do not tag waiter.Queues. Some waiter.Queues, e.g. pipe.Pipe.Queue and kernel.Task.signalQueue, are used by both VFS1 and VFS2 (the latter via signalfd); as a result of the above, tagging these Queues state:"nosave" or state:"zerovalue" breaks VFS2 epoll. Remove VFS1 epoll unregistration before saving (bringing it in line with VFS2), and remove these tags from all waiter.Queues. Also clean up after the epoll test added by cl/402323053, which implied this issue (by instantiating DisableSave in the new test) without reporting it. PiperOrigin-RevId: 402596216
Diffstat (limited to 'pkg/lisafs/sock.go')
0 files changed, 0 insertions, 0 deletions