Linux Union Filesystem

• Thread Index

• Re: Optional switching off cow in overlayfs
  • From: Jan Olszak <j.olszak@xxxxxxxxxxx>
• Re: Optional switching off cow in overlayfs
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [PATCH] SELinux: Create a common helper to determine an inode label [ver #3]
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 0/8] Security: Provide unioned file support
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 1/2] vfs: add file_path() helper
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 2/2] vfs: add seq_file_path() helper
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 1/2] vfs: add file_path() helper
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 0/8] Security: Provide unioned file support
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [PATCH 2/2] vfs: add seq_file_path() helper
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/2] vfs: add file_path() helper
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• [PATCH 2/2] vfs: add seq_file_path() helper
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [PATCH 0/8] Security: Provide unioned file support
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• [PATCH 1/2] vfs: add file_path() helper
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [PATCH 0/8] Security: Provide unioned file support
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [PATCH 0/8] Security: Provide unioned file support
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 0/8] Security: Provide unioned file support
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [PATCH 0/8] Security: Provide unioned file support
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] SELinux: Create a common helper to determine an inode label [ver #3]
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH] SELinux: Create a common helper to determine an inode label [ver #3]
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• [PATCH] SELinux: Create a common helper to determine an inode label [ver #3]
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH] SELinux: Create a common helper to determine an inode label [ver #2]
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH] SELinux: Create a common helper to determine an inode label [ver #2]
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH] SELinux: Create a common helper to determine an inode label [ver #2]
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [PATCH] SELinux: Create a common helper to determine an inode label [ver #2]
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [PATCH 5/8] SELinux: Stub in copy-up handling
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH] SELinux: Create a common helper to determine an inode label
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH] SELinux: Create a common helper to determine an inode label [ver #2]
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH] SELinux: Create a common helper to determine an inode label
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH] SELinux: Create a common helper to determine an inode label
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• [PATCH] SELinux: Create a common helper to determine an inode label
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 7/8] SELinux: Create a common helper to determine an inode label
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [PATCH 7/8] SELinux: Create a common helper to determine an inode label
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [PATCH 5/8] SELinux: Stub in copy-up handling
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• Re: [PATCH 7/8] SELinux: Create a common helper to determine an inode label
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 5/7] SELinux: Handle opening of a unioned file
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 7/8] SELinux: Create a common helper to determine an inode label
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [PATCH 7/8] SELinux: Create a common helper to determine an inode label
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 6/8] SELinux: Handle opening of a unioned file
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 7/8] SELinux: Create a common helper to determine an inode label
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [PATCH 6/8] SELinux: Handle opening of a unioned file
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [PATCH 5/8] SELinux: Stub in copy-up handling
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: Optional switching off cow in overlayfs
  • From: Jan Olszak <j.olszak@xxxxxxxxxxx>
• Re: Optional switching off cow in overlayfs
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 0/8] Security: Provide unioned file support
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 6/8] SELinux: Handle opening of a unioned file
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 7/8] SELinux: Create a common helper to determine an inode label
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 8/8] SELinux: Check against union label for file operations
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 4/8] Overlayfs: Use copy-up security hooks
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 5/8] SELinux: Stub in copy-up handling
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 3/8] Security: Provide copy-up security hooks for unioned files
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 2/8] overlayfs: Make f_path always point to the overlay and f_inode to the underlay
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 1/8] overlay: Call ovl_drop_write() earlier in ovl_dentry_open()
  • From: David Howells <dhowells@xxxxxxxxxx>
• Optional switching off cow in overlayfs
  • From: Jan Olszak <j.olszak@xxxxxxxxxxx>
• Re: [PATCH 5/7] SELinux: Handle opening of a unioned file
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [PATCH 5/7] SELinux: Handle opening of a unioned file
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [PATCH 5/7] SELinux: Handle opening of a unioned file
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 5/7] SELinux: Handle opening of a unioned file
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 5/7] SELinux: Handle opening of a unioned file
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [PATCH 5/7] SELinux: Handle opening of a unioned file
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 5/7] SELinux: Handle opening of a unioned file
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [PATCH 5/7] SELinux: Handle opening of a unioned file
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 5/7] SELinux: Handle opening of a unioned file
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [OpenWrt-Devel] Device tree issues with TL-WDR4900 (mpc85xx) and kernel 4.0.1
  • From: Roman Yeryomin <leroi.lists@xxxxxxxxx>
• Re: [PATCH 5/7] SELinux: Handle opening of a unioned file
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [OpenWrt-Devel] Device tree issues with TL-WDR4900 (mpc85xx) and kernel 4.0.1
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [OpenWrt-Devel] Device tree issues with TL-WDR4900 (mpc85xx) and kernel 4.0.1
  • From: Felix Fietkau <nbd@xxxxxxxxxxx>
• Re: [OpenWrt-Devel] Device tree issues with TL-WDR4900 (mpc85xx) and kernel 4.0.1
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Mount doesn't show subvol option for btrfs
  • From: james harvey <jamespharvey20@xxxxxxxxx>
• Re: [PATCH 5/7] SELinux: Handle opening of a unioned file
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH] overlayfs: Warn on copy up if a process has a R/O fd open to the lower file
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH] overlayfs: Warn on copy up if a process has a R/O fd open to the lower file
  • From: Colin Walters <walters@xxxxxxxxxx>
• Re: [PATCH] overlayfs: Warn on copy up if a process has a R/O fd open to the lower file
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: Overlay filesystem doesn't feed "tail -f"
  • From: David Howells <dhowells@xxxxxxxxxx>
• Overlay filesystem doesn't feed "tail -f"
  • From: james harvey <jamespharvey20@xxxxxxxxx>
• Re: [PATCH 2/2] ovl: allow distributed fs as lower layer
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH 2/2] ovl: allow distributed fs as lower layer
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Overlay filesystem bug with parallel reads & writes
  • From: james harvey <jamespharvey20@xxxxxxxxx>
• Re: [PATCH 2/2] ovl: allow distributed fs as lower layer
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH 2/2] ovl: allow distributed fs as lower layer
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [PATCH 2/2] ovl: allow distributed fs as lower layer
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• [PATCH 1/2] ovl: don't traverse automount points
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• [PATCH 2/2] ovl: allow distributed fs as lower layer
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• [PATCH 0/2] ovl: support NFS as lower layer
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: Can ovl_drop_write() be called earlier in ovl_dentry_open()
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: Can ovl_drop_write() be called earlier in ovl_dentry_open()
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: Can ovl_drop_write() be called earlier in ovl_dentry_open()
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: Can ovl_drop_write() be called earlier in ovl_dentry_open()
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• [PATCH] overlay: Call ovl_drop_write() earlier in ovl_dentry_open()
  • From: David Howells <dhowells@xxxxxxxxxx>
• Can ovl_drop_write() be called earlier in ovl_dentry_open()
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: procfs reports unexpected mnt_id and path for overlayfs files
  • From: Saied Kazemi <saied@xxxxxxxxxx>
• [PATCH] overlayfs: Warn on copy up if a process has a R/O fd open to the lower file
  • From: David Howells <dhowells@xxxxxxxxxx>
• [GIT PULL] overlayfs fixes for 4.1
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: NFS lowerdir support in mainline kernel anytime soon?
  • From: sa <sa-dev@xxxxxxxxxx>
• Re: NFS lowerdir support in mainline kernel anytime soon?
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: Bug in overlay FS
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: linux / overlay / OpenWrt / problems with full working dir
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: linux / overlay / OpenWrt / problems with full working dir
  • From: Bastian Bittorf <bittorf@xxxxxxxxxxxxxx>
• NFS lowerdir support in mainline kernel anytime soon?
  • From: sa <sa-dev@xxxxxxxxxx>
• Re: linux / overlay / OpenWrt / problems with full working dir
  • From: hujianyang <hujianyang@xxxxxxxxxx>
• Re: linux / overlay / OpenWrt / problems with full working dir
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [PATCH] unionmount-testsuite: test rmdir of non-empty opaque dir
  • From: Vincent Batts <vbatts@xxxxxxxxx>
• Re: [PATCH] unionmount-testsuite: test rmdir of non-empty opaque dir
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH] unionmount-testsuite: test rmdir of non-empty opaque dir
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: Overalyfs regression in 4.0
  • From: Jordi Pujol Palomer <jordipujolp@xxxxxxxxx>
• Re: [PATCH] unionmount-testsuite: test rmdir of non-empty opaque dir
  • From: Vincent Batts <vbatts@xxxxxxxxx>
• [PATCH] unionmount-testsuite: test rmdir of non-empty opaque dir
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: Overalyfs regression in 4.0
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Overalyfs regression in 4.0
  • From: Josh Boyer <jwboyer@xxxxxxxxxxxxxxxxx>
• Re: use scenario for overlay FS
  • From: "A. Wan" <jm@xxxxxxxxxx>
• Re: use scenario for overlay FS
  • From: Iyad Qumei <iyad.qumei@xxxxxxx>
• Re: use scenario for overlay FS
  • From: "A. Wan" <jm@xxxxxxxxxx>
• use scenario for overlay FS
  • From: Iyad Qumei <iyad.qumei@xxxxxxx>
• Re: [PATCH 3/4] Overlayfs: Wrap accesses to ->d_inode on subordinate filesystems
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [PATCH 1/4] Overlayfs: Convert S_ISDIR(dentry->d_inode) to d_is_dir()/d_can_lookup()
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 4/4] Overlayfs: Wrap RCU-mode accesses to ->d_inode on subordinate filesystems
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 3/4] Overlayfs: Wrap accesses to ->d_inode on subordinate filesystems
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 2/4] Overlayfs: Convert own ->d_inode to d_inode() or d_really_is_positive/negative()
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 1/4] Overlayfs: Convert S_ISDIR(dentry->d_inode) to d_is_dir()/d_can_lookup()
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 0/4] Overlayfs: Wrap ->d_inode
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 1/4] Overlayfs: Convert S_ISDIR(dentry->d_inode) to d_is_dir()/d_can_lookup()
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: procfs reports unexpected mnt_id and path for overlayfs files
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• procfs reports unexpected mnt_id and path for overlayfs files
  • From: Andrew Vagin <avagin@xxxxxxxx>
• Re: [PATCH 12/15] VFS: Add owner-filesystem positive/negative dentry checks
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [PATCH 12/15] VFS: Add owner-filesystem positive/negative dentry checks
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 12/15] VFS: Add owner-filesystem positive/negative dentry checks
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• [PATCH 02/15] VFS: Fix up missed bits of apparmor to use d_inode()
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 04/15] VFS: Fix up missed bits of lustre to use d_inode()
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 07/15] VFS: AF_UNIX sockets should call mknod on the top layer only
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 08/15] VFS: Cachefiles should perform fs modifications on the top layer only
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 10/15] VFS: Fix up debugfs to use d_is_dir() in place of S_ISDIR()
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 13/15] VFS: Impose ordering on accesses of d_inode and d_flags
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 15/15] VFS: Make pathwalk use d_is_reg() rather than S_ISREG()
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 14/15] VFS: Combine inode checks with d_is_negative() and d_is_positive() in pathwalk
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 12/15] VFS: Add owner-filesystem positive/negative dentry checks
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 11/15] NFS: Don't use d_inode as a variable name
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 09/15] VFS: Fix up some ->d_inode accesses in the chelsio driver
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 06/15] VFS: Fix up missed bits of reiserfs to use d_inode()
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 01/15] configfs: Fix inconsistent use of file_inode() vs file->f_path.dentry->d_inode
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 05/15] VFS: Fix up missed bits of ecryptfs to use d_inode()
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 03/15] VFS: Fix up audit to use d_backing_inode()
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 00/15] VFS: File pinning: pre-script-run fixups
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: d_path() and overlay fs
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: d_path() and overlay fs
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: d_path() and overlay fs
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: d_path() and overlay fs
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• [GIT PULL] overlayfs fixes
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [PATCH 3/3] ovl: upper fs should not be R/O
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: Small code issue
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [overlay] what's the purpose for setting RENAME_EXCHANGE when dest is WHITEOUT dev
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: stat inconsistency with overlayfs
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: stat inconsistency with overlayfs
  • From: hujianyang <hujianyang@xxxxxxxxxx>
• Re: stat inconsistency with overlayfs
  • From: Atom2 <ariel.atom2@xxxxxxxxxx>
• Re: [PATCH] ovl: free file dentry immediately
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: stat inconsistency with overlayfs
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: stat inconsistency with overlayfs
  • From: Atom2 <ariel.atom2@xxxxxxxxxx>
• Re: stat inconsistency with overlayfs
  • From: Atom2 <ariel.atom2@xxxxxxxxxx>
• Re: stat inconsistency with overlayfs
  • From: Xu Wang <xuw@xxxxxxxxxx>
• Re: stat inconsistency with overlayfs
  • From: hujianyang <hujianyang@xxxxxxxxxx>
• stat inconsistency with overlayfs
  • From: Atom2 <ariel.atom2@xxxxxxxxxx>
• Re: [GIT PULL] multi-layer support for overlay filesystem
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [GIT PULL] multi-layer support for overlay filesystem
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: Support for filesystems with d_revalidate (NFS)
  • From: "Caldwell, Blake A." <blakec@xxxxxxxx>
• Re: Support for filesystems with d_revalidate (NFS)
  • From: David Howells <dhowells@xxxxxxxxxx>
• [GIT PULL] multi-layer support for overlay filesystem
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: Support for filesystems with d_revalidate (NFS)
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: Support for filesystems with d_revalidate (NFS)
  • From: "Caldwell, Blake A." <blakec@xxxxxxxx>
• Re: Support for filesystems with d_revalidate (NFS)
  • From: Eric Jones <ejones@xxxxxxxx>
• Support for filesystems with d_revalidate (NFS)
  • From: "Caldwell, Blake A." <blakec@xxxxxxxx>
• [PATCH] ovl: free file dentry immediately
  • From: 王旭 <xuw2015@xxxxxxxxx>
• multiple lower layers with overlayfs: timeline/ETA?
  • From: intrigeri <intrigeri@xxxxxxxx>
• [overlay] what's the purpose for setting RENAME_EXCHANGE when dest is WHITEOUT dev
  • From: 王旭 <xuw2015@xxxxxxxxx>
• Small code issue
  • From: hujianyang <hujianyang@xxxxxxxxxx>
• Re: overlayfs lazy unmounts?
  • From: hujianyang <hujianyang@xxxxxxxxxx>
• Re: overlayfs lazy unmounts?
  • From: Ian Kent <raven@xxxxxxxxxx>
• Re: overlayfs lazy unmounts?
  • From: Eric Jones <ejones@xxxxxxxx>
• Re: Overlayfs, *notify() and file locking...
  • From: Jeff Layton <jeff.layton@xxxxxxxxxxxxxxx>
• Overlayfs, *notify() and file locking...
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 3/3] ovl: upper fs should not be R/O
  • From: hujianyang <hujianyang@xxxxxxxxxx>
• Re: [PATCH 3/3] ovl: upper fs should not be R/O
  • From: "A. Wan" <jm@xxxxxxxxxx>
• Re: [PATCH 3/3] ovl: upper fs should not be R/O
  • From: Seunghun Lee <waydi1@xxxxxxxxx>
• Re: [PATCH 1/3] ovl: print error message for invalid mount options
  • From: hujianyang <hujianyang@xxxxxxxxxx>
• [PATCH 3/3] ovl: upper fs should not be R/O
  • From: hujianyang <hujianyang@xxxxxxxxxx>
• [PATCH 2/3] ovl: check lowerdir amount for non-upper mount
  • From: hujianyang <hujianyang@xxxxxxxxxx>
• [PATCH 1/3] ovl: print error message for invalid mount options
  • From: hujianyang <hujianyang@xxxxxxxxxx>
• Re: Allow non-workdir mount in overlayfs?
  • From: hujianyang <hujianyang@xxxxxxxxxx>
• Re: Allow non-workdir mount in overlayfs?
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Allow non-workdir mount in overlayfs?
  • From: hujianyang <hujianyang@xxxxxxxxxx>
• Re: PROBLEM: Mounting multiple lowerdirs with "lowerdir=/tmp/a0,/tmp/a" returns 32
  • From: Fabian Sturm <fabian.sturm@xxxxxxx>
• Re: PROBLEM: Mounting multiple lowerdirs with "lowerdir=/tmp/a0,/tmp/a" returns 32
  • From: hujianyang <hujianyang@xxxxxxxxxx>
• PROBLEM: Mounting multiple lowerdirs with "lowerdir=/tmp/a0,/tmp/a" returns 32
  • From: Fabian Sturm <fabian.sturm@xxxxxxx>
• Re: [PATCH RFC resend] ovl: discard independent cursor in readdir()
  • From: hujianyang <hujianyang@xxxxxxxxxx>
• Re: [PATCH] ovl: Fix condition check for workdir
  • From: Seunghun Lee <waydi1@xxxxxxxxx>
• Re: [PATCH RFC resend] ovl: discard independent cursor in readdir()
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [PATCH] ovl: Fix condition check for workdir
  • From: hujianyang <hujianyang@xxxxxxxxxx>
• Re: [PATCH RFC resend] ovl: discard independent cursor in readdir()
  • From: hujianyang <hujianyang@xxxxxxxxxx>
• Re: Multiple lower layers - presedence?
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [PATCH] ovl: Fix opaque regression in ovl_lookup
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [PATCH] ovl: Fix kernel panic while mounting overlayfs
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [PATCH] ovl: Prevent rw remount when it should be ro mount
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• [PATCH] ovl: Fix condition check for workdir
  • From: Seunghun Lee <waydi1@xxxxxxxxx>
• Re: [PATCH] ovl: Prevent rw remount when it should be ro mount
  • From: Seunghun Lee <waydi1@xxxxxxxxx>
• Re: [PATCH] ovl: Prevent rw remount when it should be ro mount
  • From: hujianyang <hujianyang@xxxxxxxxxx>
• Re: Multiple lower layers - presedence?
  • From: hujianyang <hujianyang@xxxxxxxxxx>
• Re: Multiple lower layers - presedence?
  • From: intrigeri <intrigeri@xxxxxxxx>
• Re: [PATCH] ovl: Prevent rw remount when it should be ro mount
  • From: Seunghun Lee <waydi1@xxxxxxxxx>
• [PATCH] ovl: Fix opaque regression in ovl_lookup
  • From: hujianyang <hujianyang@xxxxxxxxxx>
• [PATCH] ovl: Fix kernel panic while mounting overlayfs
  • From: hujianyang <hujianyang@xxxxxxxxxx>
• Multiple lower layers - presedence?
  • From: Fabian Sturm <fabian.sturm@xxxxxxx>
• Re: [PATCH] ovl: Prevent rw remount when it should be ro mount
  • From: hujianyang <hujianyang@xxxxxxxxxx>
• Re: [GIT PULL] multi-layer support for overlay filesystem
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [GIT PULL] multi-layer support for overlay filesystem
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• [PATCH RFC resend] ovl: discard independent cursor in readdir()
  • From: hujianyang <hujianyang@xxxxxxxxxx>
• Re: [PATCH RFC] ovl: discard independent cursor in readdir()
  • From: hujianyang <hujianyang@xxxxxxxxxx>
• Re: [PATCH RFC] ovl: discard independent cursor in readdir()
  • From: hujianyang <hujianyang@xxxxxxxxxx>
• Problem with overlayfs and switch_root
  • From: Weng Xuetian <wengxt@xxxxxxxxx>
• [PATCH RFC] ovl: discard independent cursor in readdir()
  • From: hujianyang <hujianyang@xxxxxxxxxx>
• [PATCH resend] ovl: cleanup redundant blank lines
  • From: hujianyang <hujianyang@xxxxxxxxxx>
• Re: aufs as root vor openvz CT
  • From: Sergey Korshunoff <seyko2@xxxxxxxxx>
• [GIT PULL] multi-layer support for overlay filesystem
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: overlayfs /proc paths
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: Cursor in readdir
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: Cursor in readdir
  • From: hujianyang <hujianyang@xxxxxxxxxx>
• Re: Cursor in readdir
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Cursor in readdir
  • From: hujianyang <hujianyang@xxxxxxxxxx>
• Re: [PATCH 5/7] SELinux: Handle opening of a unioned file
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 6/7] SELinux: The copy-up operation must have read permission on the lower file
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 6/7] SELinux: The copy-up operation must have read permission on the lower file
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 5/7] SELinux: Handle opening of a unioned file
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH] ovl: Cleanup redundant blank lines
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [PATCH] ovl: Cleanup redundant blank lines
  • From: hujianyang <hujianyang@xxxxxxxxxx>
• [PATCH] ovl: Cleanup redundant blank lines
  • From: hujianyang <hujianyang@xxxxxxxxxx>
• Re: Xattr issues with overlayfs
  • From: hujianyang <hujianyang@xxxxxxxxxx>
• [PATCH] testsuite: overlayfs -> overlay
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [PULL for 3.18] overlay filesystem v24
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: Xattr issues with overlayfs
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• [PATCH] ovl: Enable opauqe setting an removing in userspace
  • From: hujianyang <hujianyang@xxxxxxxxxx>
• [PATCH] ovl: Use macros to present ovl_xattr
  • From: hujianyang <hujianyang@xxxxxxxxxx>
• Xattr issues with overlayfs
  • From: hujianyang <hujianyang@xxxxxxxxxx>
• Re: [GIT PULL] overlay filesystem fixes for 3.18
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [GIT PULL] overlay filesystem fixes for 3.18
  • From: Hans-Peter Jansen <hpj@xxxxxxxxx>
• Re: [GIT PULL] overlay filesystem fixes for 3.18
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [GIT PULL] overlay filesystem fixes for 3.18
  • From: Hans-Peter Jansen <hpj@xxxxxxxxx>
• Re: [GIT PULL] overlay filesystem fixes for 3.18
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [GIT PULL] overlay filesystem fixes for 3.18
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [GIT PULL] overlay filesystem fixes for 3.18
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• [RFC/RFT] multi-layer support for overlay filesystem
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• [GIT PULL] overlay filesystem fixes for 3.18
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: How to cope with two incompatible overlayfs formats out in the wild
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: How to cope with two incompatible overlayfs formats out in the wild
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: How to cope with two incompatible overlayfs formats out in the wild
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: How to cope with two incompatible overlayfs formats out in the wild
  • From: Andy Whitcroft <apw@xxxxxxxxxxxxx>
• How to cope with two incompatible overlayfs formats out in the wild
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [RFC PATCH] overlayfs: support more than one read-only layer
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [RFC PATCH] overlayfs: support more than one read-only layer
  • From: Jordi Pujol Palomer <jordipujolp@xxxxxxxxx>
• Re: unionfs-next branch
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: unionfs-next branch
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: unionfs-next branch
  • From: David Howells <dhowells@xxxxxxxxxx>
• unionfs-next branch
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [RFC PATCH] overlayfs: support more than one read-only layer
  • From: Erez Zadok <ezk@xxxxxxxxxxxxxxxxx>
• Re: [PATCH 3/7] SELinux: Stub in copy-up handling
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH 2/7] Overlayfs: Use copy-up security hooks
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH 1/7] Security: Provide copy-up security hooks for unioned files
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH 0/7] Security: Provide unioned file support
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: [RFC PATCH] overlayfs: support more than one read-only layer
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [PATCH 0/7] Security: Provide unioned file support
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• Re: [RFC PATCH] overlayfs: support more than one read-only layer
  • From: Jordi Pujol Palomer <jordipujolp@xxxxxxxxx>
• Re: [RFC PATCH] overlayfs: support more than one read-only layer
  • From: Patrick Frisch <patrick@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/7] Security: Provide copy-up security hooks for unioned files
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 3/7] SELinux: Stub in copy-up handling
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 2/7] Overlayfs: Use copy-up security hooks
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 3/7] SELinux: Stub in copy-up handling
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH 2/7] Overlayfs: Use copy-up security hooks
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH 1/7] Security: Provide copy-up security hooks for unioned files
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH 0/7] Security: Provide unioned file support
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• [RFC PATCH] overlayfs: support more than one read-only layer
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [PATCH 0/7] Security: Provide unioned file support
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 1/7] Security: Provide copy-up security hooks for unioned files
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 0/7] Security: Provide unioned file support
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• Re: [PATCH 0/7] Security: Provide unioned file support
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 1/7] Security: Provide copy-up security hooks for unioned files
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• Re: [PATCH 0/7] Security: Provide unioned file support
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• Re: [PATCH 6/7] SELinux: The copy-up operation must have read permission on the lower file
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [PATCH 5/7] SELinux: Handle opening of a unioned file
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 5/7] SELinux: Handle opening of a unioned file
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [PATCH 5/7] SELinux: Handle opening of a unioned file
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 5/7] SELinux: Handle opening of a unioned file
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 6/7] SELinux: The copy-up operation must have read permission on the lower file
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [PATCH 5/7] SELinux: Handle opening of a unioned file
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [PATCH 6/7] SELinux: The copy-up operation must have read permission on the lower file
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• [PATCH 0/7] Security: Provide unioned file support
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 1/7] Security: Provide copy-up security hooks for unioned files
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 2/7] Overlayfs: Use copy-up security hooks
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 3/7] SELinux: Stub in copy-up handling
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 4/7] Security: Pass the union-layer file path into security_file_open()
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 5/7] SELinux: Handle opening of a unioned file
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 6/7] SELinux: The copy-up operation must have read permission on the lower file
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 7/7] SELinux: Check against union and lower labels for file ops on lower files
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: overlayfs 3.18-rc3 General protection fault
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: overlayfs 3.18-rc3 General protection fault
  • From: Jordi Pujol Palomer <jordipujolp@xxxxxxxxx>
• Re: overlayfs 3.18-rc3 General protection fault
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• overlayfs 3.18-rc3 General protection fault
  • From: Jordi Pujol Palomer <jordipujolp@xxxxxxxxx>
• Re: read-only upperdir since overlayfs.v22 or later
  • From: "A. Wan" <jm@xxxxxxxxxx>
• Re: [PATCH] ovl: initialize ->is_cursor
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• [PATCH] ovl: initialize ->is_cursor
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [PATCH fixed] vfs: make first argument of dir_context.actor typed
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] Overlayfs: ovl_fill_merge() should use container_of() rather than direct cast
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH fixed] vfs: make first argument of dir_context.actor typed
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [PATCH] Overlayfs: ovl_fill_merge() should use container_of() rather than direct cast
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [PATCH] Overlayfs: ovl_fill_merge() should use container_of() rather than direct cast
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH] Overlayfs: ovl_fill_merge() should use container_of() rather than direct cast
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• [PATCH] Overlayfs: ovl_fill_merge() should use container_of() rather than direct cast
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [GIT PULL] overlay filesystem v25
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: [GIT PULL] overlay filesystem v25
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [GIT PULL] overlay filesystem v25
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: [GIT PULL] overlay filesystem v25
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [GIT PULL] overlay filesystem v25
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: [GIT PULL] overlay filesystem v25
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [GIT PULL] overlay filesystem v25
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: Locking problem in overlayfs
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: Locking problem in overlayfs
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: Locking problem in overlayfs
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: Locking problem in overlayfs
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Locking problem in overlayfs
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH] ovl: fix check for cursor
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• [PATCH] ovl: fix check for cursor
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [GIT PULL] overlay filesystem v25
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [GIT PULL] overlay filesystem v25
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [GIT PULL] overlay filesystem v25
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [GIT PULL] overlay filesystem v25
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [GIT PULL] overlay filesystem v25
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: [GIT PULL] overlay filesystem v25
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [GIT PULL] overlay filesystem v25
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [GIT PULL] overlay filesystem v25
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• [GIT PULL] overlay filesystem v25
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [PULL for 3.18] overlay filesystem v24
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [PULL for 3.18] overlay filesystem v24
  • From: "J. R. Okajima" <hooanon05g@xxxxxxxxx>
• Re: [PULL for 3.18] overlay filesystem v24
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: [PULL for 3.18] overlay filesystem v24
  • From: "J. R. Okajima" <hooanon05g@xxxxxxxxx>
• Re: [PULL for 3.18] overlay filesystem v24
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PULL for 3.18] overlay filesystem v24
  • From: Woody Suwalski <terraluna977@xxxxxxxxx>
• [PULL for 3.18] overlay filesystem v24
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: aufs as root vor openvz CT
  • From: Sergey Korshunoff <seyko2@xxxxxxxxx>
• Re: Race in ovl_copy_up()?
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Race in ovl_copy_up()?
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: VFS tree for 3.17?
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: VFS tree for 3.17?
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Proto-tool to produce graphical schematic of path-taking syscall errors
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: overlayfs v22 on kernel 3.15.5
  • From: "Klaus Kreil" <klaus.kreil@xxxxxxxxxxxx>
• Re: overlayfs v22 on kernel 3.15.5
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: overlayfs v22 on kernel 3.15.5
  • From: "Klaus Kreil" <klaus.kreil@xxxxxxxxxxxx>
• Re: overlayfs v22 on kernel 3.15.5
  • From: "Klaus Kreil" <klaus.kreil@xxxxxxxxxxxx>
• Re: overlayfs v22 on kernel 3.15.5
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: overlayfs v22 on kernel 3.15.5
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: overlayfs v22 on kernel 3.15.5
  • From: Miklos Szeredi <miklos@xxxxxxxxxx>
• Re: aufs as root vor openvz CT
  • From: sfjro@xxxxxxxxxxxxxxxxxxxxx
• Re: aufs as root vor openvz CT
  • From: Hans-Peter Jansen <hpj@xxxxxxxxx>