I won't apply this version, please send v3 with the changes below. On Mon, 16 Nov 2026 10:12:51 +0400, Mirian Shilakadze <[email protected]> wrote: > Changes since v1, after Pavel's review and Sashiko's:
The kernel side looks right to me: the remount test under s_umount closes the v1 race, and the s_umount -> namespace_sem order is the one mount_too_revealing() already uses. What to change for v3: 1. Patch 3: not_recursive passes on a kernel without the feature, the unknown bits already fail with EINVAL. Lock the same mount without AT_RECURSIVE first and expect success. 2. Patch 3: skip instead of failing when the test is not run as root, when user namespaces are off, or when the kernel lacks the lock bits (Sashiko's point). Probe the bits once on a scratch clone. Close the handover() fd where the other tests do not. 3. Patch 3: add a check that statmount() reports the locks the kernel raised, on a mount copied into a new user and mount namespace. Patch 2 says it does, nothing tests it. 4. Patch 2 message: say that this changes what statmount() returns in every unprivileged container, not only on locked binds. 5. Patch 1 message: say why the ve0 test went away and why AT_RECURSIVE is refused. 6. Cover letter: link v1. b4 did not connect the two revisions, it has a new ticket and a new title. -- Konstantin Khorenko, Virtuozzo Linux Kernel Team _______________________________________________ Devel mailing list [email protected] https://lists.openvz.org/mailman/listinfo/devel
