+11
−2
+10
−5
Loading
Two administrator processes may race when setting child_ns_mode as one process sets child_ns_mode to "local" and then creates a namespace, but another process changes child_ns_mode to "global" between the write and the namespace creation. The first process ends up with a namespace in "global" mode instead of "local". While this can be detected after the fact by reading ns_mode and retrying, it is fragile and error-prone. Make child_ns_mode write-once so that a namespace manager can set it once and be sure it won't change. Writing a different value after the first write returns -EBUSY. This applies to all namespaces, including init_net, where an init process can write "local" to lock all future namespaces into local mode. Fixes: eafb64f4 ("vsock: add netns to vsock core") Suggested-by:Daan De Meyer <daan.j.demeyer@gmail.com> Suggested-by:
Stefano Garzarella <sgarzare@redhat.com> Co-developed-by:
Stefano Garzarella <sgarzare@redhat.com> Signed-off-by:
Stefano Garzarella <sgarzare@redhat.com> Signed-off-by:
Bobby Eshleman <bobbyeshleman@meta.com> Reviewed-by:
Stefano Garzarella <sgarzare@redhat.com> Link: https://patch.msgid.link/20260223-vsock-ns-write-once-v3-2-c0cde6959923@meta.com Signed-off-by:
Paolo Abeni <pabeni@redhat.com>