I won't apply this version, please send v3 with the changes below.

On Mon, 16 Nov 2026 10:12:53 +0400, Mirian Shilakadze 
<[email protected]> wrote:
> Report them in the mnt_attr of statmount(), as the MOUNT_ATTR_VE_LOCK_*
> attributes that raise them, whether the host raised them or the kernel
> did, as lock_mnt_tree() does on a mount copied across user namespaces.

Item 4 of the cover letter reply: say that this is a visible change in
every unprivileged container.

lock_mnt_tree() locks every protection set on a mount copied into a
new user namespace, so mnt_attr gains bits 63..60 on most mounts of
every container, ours or LXC. A tool there that feeds mnt_attr back
into mount_setattr() attr_set got 0 before and gets EPERM now. I am
fine with that, but the message has to say it.

-- 
Konstantin Khorenko,
Virtuozzo Linux Kernel Team

_______________________________________________
Devel mailing list
[email protected]
https://lists.openvz.org/mailman/listinfo/devel

Reply via email to