Miklos Szeredi <mszeredi@xxxxxxxxxx> wrote: > > Maybe - the problem is that it's harder to manage if you've got multiple > > mounts attached to a single superblock as you can only change the superblock > > state if all the mounts are R/O. > > Not true: > > [root@veci ~]# cat /proc/self/mountinfo | grep 46 > 212 78 0:46 / /tmp/1 rw,relatime shared:153 - tmpfs tmpfs rw,seclabel > 219 78 0:46 / /tmp/2 rw,relatime shared:153 - tmpfs tmpfs rw,seclabel > [root@veci ~]# mount -oremount,ro /tmp/1 > [root@veci ~]# cat /proc/self/mountinfo | grep 46 > 212 78 0:46 / /tmp/1 ro,relatime shared:153 - tmpfs tmpfs ro,seclabel > 219 78 0:46 / /tmp/2 rw,relatime shared:153 - tmpfs tmpfs ro,seclabel > [root@veci ~]# mount -oremount,bind,rw /tmp/1 > [root@veci ~]# cat /proc/self/mountinfo | grep 46 > 212 78 0:46 / /tmp/1 rw,relatime shared:153 - tmpfs tmpfs ro,seclabel > 219 78 0:46 / /tmp/2 rw,relatime shared:153 - tmpfs tmpfs ro,seclabel > [root@veci ~]# > > R/O flag on mount and on superblock can be changed independently. Ah... I misread the code. I was looking at the check that there are no writers on a mount. David -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
