Skip to content

vfs: extend loopback (bind) mounts by mnt_flags

Herbert Poetzl lkml 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest6 patches 8 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/6vfs: add missing MNT_RDONLY and macro to checkfs/namespace.c include/linux/fs.h include/linux/mount.h+32 -240 replies
2/6vfs: propagate mnt_flags into do_loopback/vfsmountfs/namespace.c+5 -26 replies
3/6vfs: propagate vfsmount into chown_common()fs/open.c+6 -50 replies
4/6vfs: propagate the nameidata into the relevant vfs_*()fs/namei.c fs/nfsd/vfs.c fs/reiserfs/xattr.c +3 more+54 -400 replies
5/6vfs: propagate the vfsmount into *xattr()fs/xattr.c+15 -80 replies
6/6vfs: extend IS_RDONLY() checks to MNT_IS_RDONLY()arch/sparc64/solaris/fs.c fs/ext2/ioctl.c fs/ext3/ioctl.c +7 more+43 -230 replies

Reviews trailers per patch

1 of 6 patches has a Reviewed-by or Acked-by.

PatchChristoph Hellwig
1/6
2/6A-b A-b
3/6
4/6
5/6
6/6

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [PATCH 0/6] vfs: extend loopback (bind) mounts by mnt_flags

The following set of patches extends the per device 'noatime', 'nodiratime' and last but not least the 'ro' (read only) mount option to the vfs --bind mounts, allowing them to behave like any other mount, by honoring those mount flags (which are silently ignored by the current implementation in 2.4.x and 2.6.x)

the patch makes the following syscall variations behave as expected:

- open (read/write/trunc), create
- link, symlink, unlink
- mknod (reg/block/char/fifo)
- mkfifo, mkdir, rmdir, rename
- (f,l)chown, (f)chmod, utime
- access, truncate, mmap
- ioctl (gen/ext2/ext3/reiser)
- (f,l)setxattr, (f,l)removexattr

an older version of this patch was included in 2.6.0-test6-mm2, and v2.6.4-wolk2.0, the patches are in use by several people, without any issues ...

please consider inclusion (in -mm ?) and/or let me know what needs to be changed to get this functionality into mainline ...

TIA,
Herbert