Linux Union Filesystem

Thread Index

Re: [GIT PULL] overlayfs fixes for 5.2-rc6
- From: pr-tracker-bot@xxxxxxxxxx
[GIT PULL] overlayfs fixes for 5.2-rc6
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [PATCH] overlay/061: remove from auto and quick groups
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] ovl: make i_ino consistent with st_ino in more cases
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [PATCH] ovl: make i_ino consistent with st_ino in more cases
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] ovl: fix wrong flags check in FS_IOC_FS[SG]ETXATTR ioctls
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH v2] ovl: fix typo in MODULE_PARM_DESC
- From: Nicolas Schier <nicolas@xxxxxxxxx>
[PATCH] overlay/061: remove from auto and quick groups
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH] overlay: fix _scratch_remount with xfs_info 5.0.0
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH] ovl: fix bogus -Wmaybe-unitialized warning
- From: Arnd Bergmann <arnd@xxxxxxxx>
[PATCH] ovl: fix typo in MODULE_PARM_DESC
- From: "Nicolas Schier" <n.schier@xxxxxx>
Re: FAILED: patch "[PATCH] ovl: support the FS_IOC_FS[SG]ETXATTR ioctls" failed to apply to 5.1-stable tree
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH v2] locks: eliminate false positive conflicts for write lease
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH v2] locks: eliminate false positive conflicts for write lease
- From: Jeff Layton <jlayton@xxxxxxxxxx>
Re: [PATCH v2] locks: eliminate false positive conflicts for write lease
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH v2] locks: eliminate false positive conflicts for write lease
- From: Jeff Layton <jlayton@xxxxxxxxxx>
Re: [PATCH v2] locks: eliminate false positive conflicts for write lease
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH v2] locks: eliminate false positive conflicts for write lease
- From: "J . Bruce Fields" <bfields@xxxxxxxxxxxx>
Re: [PATCH v2] locks: eliminate false positive conflicts for write lease
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [PATCH v2] locks: eliminate false positive conflicts for write lease
- From: "J . Bruce Fields" <bfields@xxxxxxxxxxxx>
Re: [PATCH v2] locks: eliminate false positive conflicts for write lease
- From: "J . Bruce Fields" <bfields@xxxxxxxxxxxx>
[PATCH v2] locks: eliminate false positive conflicts for write lease
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH 1/2] vfs: replace i_readcount with a biased i_count
- From: Mimi Zohar <zohar@xxxxxxxxxxxxx>
Re: [PATCH 1/2] vfs: replace i_readcount with a biased i_count
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH 1/2] vfs: replace i_readcount with a biased i_count
- From: "J . Bruce Fields" <bfields@xxxxxxxxxxxx>
Re: [PATCH 1/2] vfs: replace i_readcount with a biased i_count
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH 1/2] vfs: replace i_readcount with a biased i_count
- From: Mimi Zohar <zohar@xxxxxxxxxxxxx>
Re: [PATCH v2] overlay: allow config override of metacopy/redirect defaults
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: [PATCH v2] overlay: allow config override of metacopy/redirect defaults
- From: Daniel Walsh <dwalsh@xxxxxxxxxx>
Re: [PATCH v2] overlay: allow config override of metacopy/redirect defaults
- From: Matt Coffin <mcoffin13@xxxxxxxxx>
Re: [PATCH v2] overlay: allow config override of metacopy/redirect defaults
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: [PATCH v2] overlay: allow config override of metacopy/redirect defaults
- From: Daniel Walsh <dwalsh@xxxxxxxxxx>
[PATCH 3/3] generic: check CAP_LINUX_IMMUTABLE capability with FS_IOC_FSSETXATTR
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH 2/3] fstests: check for filesystem FS_IOC_FSSETXATTR support
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH 1/3] fstests: print out xfs_io parameter when command fails
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH 0/3] Improved FS_IOC_FSSETXATTR tests
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH] ovl: fix wrong flags check in FS_IOC_FS[SG]ETXATTR ioctls
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] ovl: make i_ino consistent with st_ino in more cases
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [PATCH v2] overlay: allow config override of metacopy/redirect defaults
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: [PATCH v2] overlay: allow config override of metacopy/redirect defaults
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [PATCH v2] overlay: allow config override of metacopy/redirect defaults
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH v2] overlay: allow config override of metacopy/redirect defaults
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: [PATCH v2] overlay: allow config override of metacopy/redirect defaults
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: [PATCH v2] overlay: allow config override of metacopy/redirect defaults
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: [PATCH 1/2] vfs: replace i_readcount with a biased i_count
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [PATCH v2] overlay: allow config override of metacopy/redirect defaults
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
[PATCH] ovl: make i_ino consistent with st_ino in more cases
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] overlay: Display redirect_dir mount option when it is set automatically
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH v2] overlay: allow config override of metacopy/redirect defaults
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH] overlay: Display redirect_dir mount option when it is set automatically
- From: Matt Coffin <mcoffin13@xxxxxxxxx>
Re: [PATCH v2] overlay: allow config override of metacopy/redirect defaults
- From: Matt Coffin <mcoffin13@xxxxxxxxx>
[PATCH 2/2] locks: eliminate false positive conflicts for write lease
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH 1/2] vfs: replace i_readcount with a biased i_count
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH 0/2] Fix write leases on overlayfs
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH v2] overlay: allow config override of metacopy/redirect defaults
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH v2] overlay: allow config override of metacopy/redirect defaults
- From: Matt Coffin <mcoffin13@xxxxxxxxx>
[PATCH] overlay: allow config override of metacopy/redirect defaults
- From: Matt Coffin <mcoffin13@xxxxxxxxx>
Re: [GIT PULL] overlayfs fixes for 5.2-rc4
- From: pr-tracker-bot@xxxxxxxxxx
[GIT PULL] overlayfs fixes for 5.2-rc4
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [PATCH v2 2/2] fanotify06: Close all file descriptors of read events
- From: Petr Vorel <pvorel@xxxxxxx>
[PATCH v2 2/2] fanotify06: Close all file descriptors of read events
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH v2 1/2] fanotify06: add a test case for overlayfs
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: which lower filesystems are actually supported?
- From: Gabriel Krisman Bertazi <krisman@xxxxxxxxxxxxx>
Re: which lower filesystems are actually supported?
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: which lower filesystems are actually supported?
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: which lower filesystems are actually supported?
- From: "Theodore Ts'o" <tytso@xxxxxxx>
Re: [PATCH v3 3/4] overlay: correct fsck.overlay exit code
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH v3 3/4] overlay: correct fsck.overlay exit code
- From: Eryu Guan <guaneryu@xxxxxxxxx>
Re: which lower filesystems are actually supported?
- From: Amir Goldstein <amir73il@xxxxxxxxx>
which lower filesystems are actually supported?
- From: Marco Nelissen <marco.nelissen@xxxxxxxxx>
[PATCH AUTOSEL 5.1 067/186] ovl: do not generate duplicate fsnotify events for "fake" path
- From: Sasha Levin <sashal@xxxxxxxxxx>
[PATCH AUTOSEL 5.0 062/173] ovl: do not generate duplicate fsnotify events for "fake" path
- From: Sasha Levin <sashal@xxxxxxxxxx>
[PATCH AUTOSEL 4.19 049/141] ovl: do not generate duplicate fsnotify events for "fake" path
- From: Sasha Levin <sashal@xxxxxxxxxx>
Re: [PATCH v3 3/4] overlay: correct fsck.overlay exit code
- From: "zhangyi (F)" <yi.zhang@xxxxxxxxxx>
Re: [PATCH v3 2/4] overlay: fix _repair_scratch_fs
- From: "zhangyi (F)" <yi.zhang@xxxxxxxxxx>
Re: [PATCH v3 1/4] fstests: define constants for fsck exit codes
- From: "zhangyi (F)" <yi.zhang@xxxxxxxxxx>
Re: [bug report] ovl: detect overlapping layers
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[bug report] ovl: detect overlapping layers
- From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
[PATCH v3 3/4] overlay: correct fsck.overlay exit code
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH v3 4/4] overlay: fix exit code for some fsck.overlay valid cases
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH v3 2/4] overlay: fix _repair_scratch_fs
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH v3 1/4] fstests: define constants for fsck exit codes
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH v3 0/4] Misc. fsck.overlay test fixes
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH] overlay: Test mount error cases with overlapping layers
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH v2] ovl: detect overlapping layers
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [PATCH v2] ovl: detect overlapping layers
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] ovl: support the FS_IOC_FS[SG]ETXATTR ioctls
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
[PATCH] ovl: support the FS_IOC_FS[SG]ETXATTR ioctls
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [LTP] [PATCH] [COMMITTED] syscalls/fcntl33: Fix typo overlapfs -> overlayfs
- From: Cyril Hrubis <chrubis@xxxxxxx>
Re: [LTP] [PATCH] [COMMITTED] syscalls/fcntl33: Fix typo overlapfs -> overlayfs
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [LTP] [PATCH] [COMMITTED] syscalls/fcntl33: Fix typo overlapfs -> overlayfs
- From: Cyril Hrubis <chrubis@xxxxxxx>
Re: [LTP] [PATCH] [COMMITTED] syscalls/fcntl33: Fix typo overlapfs -> overlayfs
- From: Petr Vorel <pvorel@xxxxxxx>
Re: [LTP] [PATCH] [COMMITTED] syscalls/fcntl33: Fix typo overlapfs -> overlayfs
- From: "J. Bruce Fields" <bfields@xxxxxxxxxxxx>
Re: [LTP] [PATCH] [COMMITTED] syscalls/fcntl33: Fix typo overlapfs -> overlayfs
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [LTP] [PATCH] [COMMITTED] syscalls/fcntl33: Fix typo overlapfs -> overlayfs
- From: "J. Bruce Fields" <bfields@xxxxxxxxxxxx>
Re: [LTP] [PATCH] [COMMITTED] syscalls/fcntl33: Fix typo overlapfs -> overlayfs
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH 12/11] man-pages: copy_file_range updates
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH 01/11] vfs: copy_file_range source range over EOF should fail
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH 01/11] vfs: copy_file_range source range over EOF should fail
- From: Olga Kornievskaia <olga.kornievskaia@xxxxxxxxx>
Re: [PATCH 01/11] vfs: copy_file_range source range over EOF should fail
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH 01/11] vfs: copy_file_range source range over EOF should fail
- From: Olga Kornievskaia <olga.kornievskaia@xxxxxxxxx>
Re: [PATCH 01/11] vfs: copy_file_range source range over EOF should fail
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [GIT PULL] overlayfs update for 5.2
- From: pr-tracker-bot@xxxxxxxxxx
[GIT PULL] overlayfs update for 5.2
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [PATCH] overlayfs: ignore empty NFSv4 ACLs in ext4 upperdir
- From: "J. Bruce Fields" <bfields@xxxxxxxxxxxx>
Re: [PATCH v2] fs: Fix ovl_i_mutex_dir_key/p->lock/cred cred_guard_mutex deadlock
- From: Mina Almasry <almasrymina@xxxxxxxxxx>
Re: [PATCH] generic: add a testcase to check the capability CAP_LINUX_IMMUTABLE
- From: Eryu Guan <guaneryu@xxxxxxxxx>
Re: [PATCH] ovl: relax WARN_ON() for overlapping layers use case
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [PATCH] ovl: relax WARN_ON() for overlapping layers use case
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] generic: add a testcase to check the capability CAP_LINUX_IMMUTABLE
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH] generic: add a testcase to check the capability CAP_LINUX_IMMUTABLE
- From: Jiufei Xue <jiufei.xue@xxxxxxxxxxxxxxxxx>
Re: [PATCH v2] generic: add a testcase to check the capability CAP_LINUX_IMMUTABLE
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH v2] generic: add a testcase to check the capability CAP_LINUX_IMMUTABLE
- From: Jiufei Xue <jiufei.xue@xxxxxxxxxxxxxxxxx>
Re: [PATCH] overlayfs: ignore empty NFSv4 ACLs in ext4 upperdir
- From: "J. Bruce Fields" <bfields@xxxxxxxxxxxx>
Re: [PATCH] generic: add a testcase to check the capability CAP_LINUX_IMMUTABLE
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH] generic: add a testcase to check the capability CAP_LINUX_IMMUTABLE
- From: Jiufei Xue <jiufei.xue@xxxxxxxxxxxxxxxxx>
Re: [PATCH] overlayfs: ignore empty NFSv4 ACLs in ext4 upperdir
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [PATCH] overlayfs: ignore empty NFSv4 ACLs in ext4 upperdir
- From: NeilBrown <neilb@xxxxxxxx>
Re: [PATCH v2] overlayfs: check the capability before cred overridden
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [PATCH v2] ovl: do not generate duplicate fsnotify events for "fake" path
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
[PATCH v2] overlayfs: check the capability before cred overridden
- From: Jiufei Xue <jiufei.xue@xxxxxxxxxxxxxxxxx>
Re: [PATCH v2] ovl: support stacked SEEK_HOLE/SEEK_DATA
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [PATCH] ovl: fix missing upper fs freeze protection on copy up for ioctl
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [PATCH] overlayfs: check the capability before cred overridden
- From: Jiufei Xue <jiufei.xue@xxxxxxxxxxxxxxxxx>
Re: [PATCH] overlayfs: check the capability before cred overridden
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] overlayfs: check the capability before cred overridden
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH] overlayfs: check the capability before cred overridden
- From: Jiufei Xue <jiufei.xue@xxxxxxxxxxxxxxxxx>
Re: [bug report] chattr +i succeed in docker which don‘t have the capability CAP_LINUX_IMMUTABLE
- From: Jiufei Xue <jiufei.xue@xxxxxxxxxxxxxxxxx>
Re: [bug report] chattr +i succeed in docker which don‘t have the capability CAP_LINUX_IMMUTABLE
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[bug report] chattr +i succeed in docker which don‘t have the capability CAP_LINUX_IMMUTABLE
- From: Jiufei Xue <jiufei.xue@xxxxxxxxxxxxxxxxx>
Re: [PATCH] overlayfs: ignore empty NFSv4 ACLs in ext4 upperdir
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: [PATCH] overlayfs: ignore empty NFSv4 ACLs in ext4 upperdir
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] overlayfs: ignore empty NFSv4 ACLs in ext4 upperdir
- From: "Goetz, Patrick G" <pgoetz@xxxxxxxxxxxxxxx>
Re: [PATCH] overlayfs: ignore empty NFSv4 ACLs in ext4 upperdir
- From: "J. Bruce Fields" <bfields@xxxxxxxxxxxx>
Re: [PATCH] overlayfs: ignore empty NFSv4 ACLs in ext4 upperdir
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] overlayfs: ignore empty NFSv4 ACLs in ext4 upperdir
- From: "J. Bruce Fields" <bfields@xxxxxxxxxxxx>
Re: [PATCH] overlayfs: ignore empty NFSv4 ACLs in ext4 upperdir
- From: "J. Bruce Fields" <bfields@xxxxxxxxxxxx>
Re: [PATCH] overlayfs: ignore empty NFSv4 ACLs in ext4 upperdir
- From: Andreas Grünbacher <andreas.gruenbacher@xxxxxxxxx>
Re: [PATCH] overlayfs: ignore empty NFSv4 ACLs in ext4 upperdir
- From: NeilBrown <neilb@xxxxxxxx>
Re: [PATCH] OVL: add honoracl=off mount option.
- From: NeilBrown <neilb@xxxxxxxx>
Re: [PATCH] overlayfs: ignore empty NFSv4 ACLs in ext4 upperdir
- From: NeilBrown <neilb@xxxxxxxx>
Re: [PATCH] overlayfs: ignore empty NFSv4 ACLs in ext4 upperdir
- From: "Goetz, Patrick G" <pgoetz@xxxxxxxxxxxxxxx>
Re: [PATCH] overlayfs: ignore empty NFSv4 ACLs in ext4 upperdir
- From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
Re: [PATCH] overlayfs: ignore empty NFSv4 ACLs in ext4 upperdir
- From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
Re: [PATCH] overlayfs: ignore empty NFSv4 ACLs in ext4 upperdir
- From: "Goetz, Patrick G" <pgoetz@xxxxxxxxxxxxxxx>
Re: [PATCH] overlayfs: ignore empty NFSv4 ACLs in ext4 upperdir
- From: "J. Bruce Fields" <bfields@xxxxxxxxxxxx>
Re: [PATCH] overlayfs: ignore empty NFSv4 ACLs in ext4 upperdir
- From: Andreas Grünbacher <andreas.gruenbacher@xxxxxxxxx>
Re: [PATCH] overlayfs: ignore empty NFSv4 ACLs in ext4 upperdir
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [PATCH] overlayfs: ignore empty NFSv4 ACLs in ext4 upperdir
- From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
Re: [PATCH] OVL: add honoracl=off mount option.
- From: "J. R. Okajima" <hooanon05g@xxxxxxxxx>
Re: [PATCH] OVL: add honoracl=off mount option.
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] OVL: add honoracl=off mount option.
- From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
[PATCH] OVL: add honoracl=off mount option.
- From: NeilBrown <neilb@xxxxxxxx>
Re: [PATCH] overlayfs: ignore empty NFSv4 ACLs in ext4 upperdir
- From: NeilBrown <neilb@xxxxxxxx>
Re: [PATCH] overlayfs: ignore empty NFSv4 ACLs in ext4 upperdir
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] overlayfs: ignore empty NFSv4 ACLs in ext4 upperdir
- From: NeilBrown <neilb@xxxxxxxx>
WARNING in ovl_rename
- From: syzbot <syzbot+bb1836a212e69f8e201a@xxxxxxxxxxxxxxxxxxxxxxxxx>
Re: [LTP] [PATCH] fanotify06: add a test case for overlayfs
- From: Petr Vorel <pvorel@xxxxxxx>
Re: [PATCH v2] ovl: do not generate duplicate fsnotify events for "fake" path
- From: Murphy Zhou <jencce.kernel@xxxxxxxxx>
Re: [PATCH v2] ovl: do not generate duplicate fsnotify events for "fake" path
- From: kbuild test robot <lkp@xxxxxxxxx>
[PATCH v2] ovl: do not generate duplicate fsnotify events for "fake" path
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] fsnotify: do not generate duplicate events for "fake" path
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] fsnotify: do not generate duplicate events for "fake" path
- From: Jan Kara <jack@xxxxxxx>
[PATCH] fsnotify: do not generate duplicate events for "fake" path
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] fanotify06: add a test case for overlayfs
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH v2] fs: Fix ovl_i_mutex_dir_key/p->lock/cred cred_guard_mutex deadlock
- From: Mina Almasry <almasrymina@xxxxxxxxxx>
Re: [PATCH] fs: Fix ovl_i_mutex_dir_key/p->lock/cred cred_guard_mutex deadlock
- From: Mina Almasry <almasrymina@xxxxxxxxxx>
Re: [PATCH] ovl: add RWF_NONITIFY flag to skip wrong duplicate fanotify event
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] ovl: add RWF_NONITIFY flag to skip wrong duplicate fanotify event
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] fs: Fix ovl_i_mutex_dir_key/p->lock/cred cred_guard_mutex deadlock
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [PATCH] ovl: add RWF_NONITIFY flag to skip wrong duplicate fanotify event
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [PATCH] ovl: add RWF_NONITIFY flag to skip wrong duplicate fanotify event
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] ovl: add RWF_NONITIFY flag to skip wrong duplicate fanotify event
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [PATCH] ovl: add RWF_NONITIFY flag to skip wrong duplicate fanotify event
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] ovl: add RWF_NONITIFY flag to skip wrong duplicate fanotify event
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [PATCH] ovl: add RWF_NONITIFY flag to skip wrong duplicate fanotify event
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH] ovl: add RWF_NONITIFY flag to skip wrong duplicate fanotify event
- From: Murphy Zhou <jencce.kernel@xxxxxxxxx>
Re: WARNING in ovl_instantiate
- From: Dmitry Vyukov <dvyukov@xxxxxxxxxx>
Re: WARNING in ovl_instantiate
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: WARNING in ovl_instantiate
- From: Dmitry Vyukov <dvyukov@xxxxxxxxxx>
Re: WARNING in ovl_instantiate
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: WARNING in ovl_instantiate
- From: syzbot <syzbot+9c69c282adc4edd2b540@xxxxxxxxxxxxxxxxxxxxxxxxx>
Re: possible deadlock in path_openat
- From: syzbot <syzbot+a55ccfc8a853d3cff213@xxxxxxxxxxxxxxxxxxxxxxxxx>
Re: WARNING in ovl_instantiate
- From: syzbot <syzbot+9c69c282adc4edd2b540@xxxxxxxxxxxxxxxxxxxxxxxxx>
Re: possible deadlock in path_openat
- From: syzbot <syzbot+a55ccfc8a853d3cff213@xxxxxxxxxxxxxxxxxxxxxxxxx>
[PATCH v2] ovl: detect overlapping layers
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: OverlaysFS
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: OverlaysFS
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: fanotify and LSM path hooks
- From: Jan Kara <jack@xxxxxxx>
Re: [PATCH v2 5/5] fscrypt: fix race where ->lookup() marks plaintext dentry as ciphertext
- From: "Theodore Ts'o" <tytso@xxxxxxx>
Re: fanotify and LSM path hooks
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [PATCH v2 4/5] fscrypt: only set dentry_operations on ciphertext dentries
- From: "Theodore Ts'o" <tytso@xxxxxxx>
Re: [PATCH v2 3/5] fs, fscrypt: clear DCACHE_ENCRYPTED_NAME when unaliasing directory
- From: "Theodore Ts'o" <tytso@xxxxxxx>
Re: fanotify and LSM path hooks
- From: Jan Kara <jack@xxxxxxx>
Re: [PATCH v2 2/5] fscrypt: fix race allowing rename() and link() of ciphertext dentries
- From: "Theodore Ts'o" <tytso@xxxxxxx>
Re: [PATCH v2 1/5] fscrypt: clean up and improve dentry revalidation
- From: "Theodore Ts'o" <tytso@xxxxxxx>
Re: fanotify and LSM path hooks
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: fanotify and LSM path hooks
- From: Jan Kara <jack@xxxxxxx>
Re: possible deadlock in seq_read (2)
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [PATCH v2 1/5] fscrypt: clean up and improve dentry revalidation
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
Re: [PATCH v2 1/5] fscrypt: clean up and improve dentry revalidation
- From: "Theodore Ts'o" <tytso@xxxxxxx>
Re: fanotify and LSM path hooks
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] ovl: Introduce mount option hide_paths
- From: Michael Weiß <michael.weiss@xxxxxxxxxxxxxxxxxxx>
Re: [PATCH] ovl: Introduce mount option hide_paths
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] ovl: Introduce mount option hide_paths
- From: Michael Weiß <michael.weiss@xxxxxxxxxxxxxxxxxxx>
Re: [PATCH] ovl: Introduce mount option hide_paths
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
[PATCH] ovl: Introduce mount option hide_paths
- From: Michael Weiß <michael.weiss@xxxxxxxxxxxxxxxxxxx>
Re: [PATCH v2 0/5] fscrypt: d_revalidate fixes and cleanups
- From: Richard Weinberger <richard@xxxxxx>
Re: [PATCH] ovl: detect overlapping layers
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: [PATCH] ovl: detect overlapping layers
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] ovl: detect overlapping layers
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: [PATCH v3 1/2] fstests: Add more sanity to seek_sanity_test
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH v3 1/2] fstests: Add more sanity to seek_sanity_test
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
Re: [PATCH v2] ovl: support stacked SEEK_HOLE/SEEK_DATA
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH v3 2/2] generic: Test that SEEK_HOLE can find a punched hole
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH v3 1/2] fstests: Add more sanity to seek_sanity_test
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH] ovl: detect overlapping layers
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] ovl: relax WARN_ON() for overlapping layers use case
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH v2 0/5] fscrypt: d_revalidate fixes and cleanups
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
Re: [Help]Cannot read symbolic link(Invalid argument) in overlayfs
- From: koishi komeiji <maykagura@xxxxxxxxx>
Re: [Help]Cannot read symbolic link(Invalid argument) in overlayfs
- From: koishi komeiji <maykagura@xxxxxxxxx>
Re: [PATCH] ovl: relax WARN_ON() for overlapping layers use case
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] ovl: relax WARN_ON() for overlapping layers use case
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [PATCH] ovl: relax WARN_ON() for overlapping layers use case
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] ovl: relax WARN_ON() for overlapping layers use case
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: [Help]Cannot read symbolic link(Invalid argument) in overlayfs
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [Help]Cannot read symbolic link(Invalid argument) in overlayfs
- From: koishi komeiji <maykagura@xxxxxxxxx>
Re: [Help]Cannot read symbolic link(Invalid argument) in overlayfs
- From: koishi komeiji <maykagura@xxxxxxxxx>
Re: [PATCH] ovl: relax WARN_ON() for overlapping layers use case
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] ovl: relax WARN_ON() for overlapping layers use case
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
[PATCH] ovl: relax WARN_ON() for overlapping layers use case
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [Help]Cannot read symbolic link(Invalid argument) in overlayfs
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] ovl: fix missing upper fs freeze protection on copy up for ioctl
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH v2] ovl: support stacked SEEK_HOLE/SEEK_DATA
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[Help]Cannot read symbolic link(Invalid argument) in overlayfs
- From: koishi komeiji <maykagura@xxxxxxxxx>
Re: WARNING in ovl_instantiate
- From: syzbot <syzbot+9c69c282adc4edd2b540@xxxxxxxxxxxxxxxxxxxxxxxxx>
[PATCH v2 1/5] fscrypt: clean up and improve dentry revalidation
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
[PATCH v2 2/5] fscrypt: fix race allowing rename() and link() of ciphertext dentries
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
[PATCH v2 0/5] fscrypt: d_revalidate fixes and cleanups
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
[PATCH v2 5/5] fscrypt: fix race where ->lookup() marks plaintext dentry as ciphertext
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
[PATCH v2 3/5] fs, fscrypt: clear DCACHE_ENCRYPTED_NAME when unaliasing directory
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
[PATCH v2 4/5] fscrypt: only set dentry_operations on ciphertext dentries
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
Re: [PATCH 1/5] fscrypt: clean up and improve dentry revalidation
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
Re: [PATCH 1/5] fscrypt: clean up and improve dentry revalidation
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
Re: [PATCH 1/5] fscrypt: clean up and improve dentry revalidation
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
[PATCH 4/5] fscrypt: only set dentry_operations on ciphertext dentries
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
[PATCH 5/5] fscrypt: fix race where ->lookup() marks plaintext dentry as ciphertext
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
[PATCH 1/5] fscrypt: clean up and improve dentry revalidation
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
[PATCH 3/5] fs, fscrypt: clear DCACHE_ENCRYPTED_NAME when unaliasing directory
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
[PATCH 2/5] fscrypt: fix race allowing rename() and link() of ciphertext dentries
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
[PATCH 0/5] fscrypt: d_revalidate fixes and cleanups
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
Re: [PATCH] ovl: Don't open files with O_NOATIME in lowerdir
- From: aszlig <aszlig@nix.build>
Re: [PATCH] ovl: Don't open files with O_NOATIME in lowerdir
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH] ovl: Don't open files with O_NOATIME in lowerdir
- From: aszlig <aszlig@nix.build>
Re: [PATCH 4/4] ubifs: Implement new mount option, fscrypt_key_required
- From: Richard Weinberger <richard@xxxxxx>
Re: [PATCH 4/4] ubifs: Implement new mount option, fscrypt_key_required
- From: "Theodore Ts'o" <tytso@xxxxxxx>
Re: [PATCH 4/4] ubifs: Implement new mount option, fscrypt_key_required
- From: Richard Weinberger <richard@xxxxxx>
Re: [PATCH 4/4] ubifs: Implement new mount option, fscrypt_key_required
- From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
Re: [PATCH 4/4] ubifs: Implement new mount option, fscrypt_key_required
- From: "Theodore Ts'o" <tytso@xxxxxxx>
Re: [PATCH 4/4] ubifs: Implement new mount option, fscrypt_key_required
- From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
Re: [PATCH 4/4] ubifs: Implement new mount option, fscrypt_key_required
- From: "Theodore Ts'o" <tytso@xxxxxxx>
Re: [PATCH 4/4] ubifs: Implement new mount option, fscrypt_key_required
- From: Richard Weinberger <richard@xxxxxx>
Re: Failure to execute file on overlayfs during switch_root/chroot
- From: aszlig <aszlig@nix.build>
Re: Failure to execute file on overlayfs during switch_root/chroot
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH 4/4] ubifs: Implement new mount option, fscrypt_key_required
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
[RFC] fscrypt_key_required mount option
- From: Richard Weinberger <richard@xxxxxx>
[PATCH 4/4] ubifs: Implement new mount option, fscrypt_key_required
- From: Richard Weinberger <richard@xxxxxx>
[PATCH 3/4] ubifs: Simplify fscrypt_get_encryption_info() error handling
- From: Richard Weinberger <richard@xxxxxx>
[PATCH 2/4] fscrypt: Export fscrypt_d_ops
- From: Richard Weinberger <richard@xxxxxx>
[PATCH 1/4] fscrypt: Implement FS_CFLG_OWN_D_OPS
- From: Richard Weinberger <richard@xxxxxx>
Re: Failure to execute file on overlayfs during switch_root/chroot
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: Failure to execute file on overlayfs during switch_root/chroot
- From: aszlig <aszlig@nix.build>
Re: Failure to execute file on overlayfs during switch_root/chroot
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: overlayfs vs. fscrypt
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: Failure to execute file on overlayfs during switch_root/chroot
- From: aszlig <aszlig@nix.build>
Re: Failure to execute file on overlayfs during switch_root/chroot
- From: aszlig <aszlig@nix.build>
Re: overlayfs vs. fscrypt
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
Re: overlayfs vs. fscrypt
- From: Richard Weinberger <richard@xxxxxx>
Re: overlayfs vs. fscrypt
- From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
Re: overlayfs vs. fscrypt
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
Re: overlayfs vs. fscrypt
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
Re: overlayfs vs. fscrypt
- From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
Re: overlayfs vs. fscrypt
- From: Richard Weinberger <richard@xxxxxx>
Re: overlayfs vs. fscrypt
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
Re: overlayfs vs. fscrypt
- From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
Re: overlayfs vs. fscrypt
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
Re: overlayfs vs. fscrypt
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
Re: overlayfs vs. fscrypt
- From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
Re: overlayfs vs. fscrypt
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
Re: overlayfs vs. fscrypt
- From: "Theodore Ts'o" <tytso@xxxxxxx>
Re: overlayfs vs. fscrypt
- From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
Re: overlayfs vs. fscrypt
- From: "Theodore Ts'o" <tytso@xxxxxxx>
Re: overlayfs vs. fscrypt
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
Re: overlayfs vs. fscrypt
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
Re: overlayfs vs. fscrypt
- From: Richard Weinberger <richard@xxxxxx>
Re: overlayfs vs. fscrypt
- From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
Re: overlayfs vs. fscrypt
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
Re: overlayfs vs. fscrypt
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
Re: overlayfs vs. fscrypt
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
Re: overlayfs vs. fscrypt
- From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
Re: overlayfs vs. fscrypt
- From: Richard Weinberger <richard@xxxxxx>
Re: overlayfs vs. fscrypt
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
Re: overlayfs vs. fscrypt
- From: "Theodore Ts'o" <tytso@xxxxxxx>
Re: overlayfs vs. fscrypt
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
Re: overlayfs vs. fscrypt
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: overlayfs vs. fscrypt
- From: Richard Weinberger <richard@xxxxxx>
Re: overlayfs vs. fscrypt
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: overlayfs vs. fscrypt
- From: Richard Weinberger <richard@xxxxxx>
Re: overlayfs vs. fscrypt
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: overlayfs vs. fscrypt
- From: Richard Weinberger <richard@xxxxxx>
Re: overlayfs vs. fscrypt
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
overlayfs vs. fscrypt
- From: Richard Weinberger <richard@xxxxxx>
Re: [GIT PULL] overlayfs update for 5.1
- From: pr-tracker-bot@xxxxxxxxxx
[GIT PULL] overlayfs update for 5.1
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [Help]Cannot read symbolic link, Invalid argument
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[Help]Cannot read symbolic link, Invalid argument
- From: kagamine rinfans <maykagura@xxxxxxxxx>
Re: [PATCH v2 2/2] generic: Test that SEEK_HOLE can find a punched hole
- From: Eryu Guan <guaneryu@xxxxxxxxx>
Re: [PATCH v2 1/2] fstests: Add more sanity to seek_sanity_test
- From: Eryu Guan <guaneryu@xxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Stephen Smalley <sds@xxxxxxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Mark Salyzyn <salyzyn@xxxxxxxxxxx>
[PATCH v2 2/2] generic: Test that SEEK_HOLE can find a punched hole
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH v2 1/2] fstests: Add more sanity to seek_sanity_test
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH 2/2] generic: Test that SEEK_HOLE can find a punched hole
- From: Eryu Guan <guaneryu@xxxxxxxxx>
Re: [PATCH 2/2] generic: Test that SEEK_HOLE can find a punched hole
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH 1/2] generic/{436,445}: check falloc support
- From: Eryu Guan <guaneryu@xxxxxxxxx>
Re: [PATCH 2/2] generic: Test that SEEK_HOLE can find a punched hole
- From: Eryu Guan <guaneryu@xxxxxxxxx>
Re: [PATCH] ovl: fix missing upper fs freeze protection on copy up for ioctl
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH v2] ovl: support stacked SEEK_HOLE/SEEK_DATA
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] ovl: support stacked SEEK_HOLE/SEEK_DATA
- From: Eddie Horng <eddiehorng.tw@xxxxxxxxx>
Re: [PATCH] ovl: support stacked SEEK_HOLE/SEEK_DATA
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [PATCH] ovl: support stacked SEEK_HOLE/SEEK_DATA
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] ovl: support stacked SEEK_HOLE/SEEK_DATA
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [PATCH] ovl: support stacked SEEK_HOLE/SEEK_DATA
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] ovl: support stacked SEEK_HOLE/SEEK_DATA
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
[PATCH] ovl: support stacked SEEK_HOLE/SEEK_DATA
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH][RESEND] kernel/acct.c: fix locking order when switching acct files
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH 2/2] generic: Test that SEEK_HOLE can find a punched hole
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH 1/2] generic/{436,445}: check falloc support
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: real_inode->i_fop->llseek is not called by ovl_llseek
- From: Amir Goldstein <amir73il@xxxxxxxxx>
real_inode->i_fop->llseek is not called by ovl_llseek
- From: Eddie Horng <eddiehorng.tw@xxxxxxxxx>
Re: [RFC PATCH 0/5] Fix overlayfs on EVM
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [RFC PATCH 0/5] Fix overlayfs on EVM
- From: Fabian Vogt <fvogt@xxxxxxx>
Re: [RFC PATCH 0/5] Fix overlayfs on EVM
- From: Mimi Zohar <zohar@xxxxxxxxxxxxx>
Re: possible deadlock in pipe_lock (2)
- From: Jan Kara <jack@xxxxxxx>
Re: possible deadlock in pipe_lock (2)
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [RFC PATCH 0/5] Fix overlayfs on EVM
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: possible deadlock in pipe_lock (2)
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: possible deadlock in pipe_lock (2)
- From: Jan Kara <jack@xxxxxxx>
Re: [RFC PATCH 0/5] Fix overlayfs on EVM
- From: Fabian Vogt <fvogt@xxxxxxx>
Re: [RFC][PATCH v2 0/5] Experiments with overlayfs filemap
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [RFC][PATCH v2 0/5] Experiments with overlayfs filemap
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [RFC PATCH 0/5] Fix overlayfs on EVM
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH 4/5] Ignore IMA / EVM xattrs during copy_up
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: possible deadlock in pipe_lock (2)
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH 5/5] Use __vfs_getxattr to get overlayfs xattrs
- From: Ignaz Forster <iforster@xxxxxxxx>
[PATCH 4/5] Ignore IMA / EVM xattrs during copy_up
- From: Ignaz Forster <iforster@xxxxxxxx>
[PATCH 3/5] Execute IMA post create hook in vfs_create
- From: Ignaz Forster <iforster@xxxxxxxx>
[PATCH 2/5] Rename ima_post_create_tmpfile
- From: Ignaz Forster <iforster@xxxxxxxx>
[PATCH 1/5] evm: instead of using the overlayfs i_ino, use the real i_ino
- From: Ignaz Forster <iforster@xxxxxxxx>
[RFC PATCH 0/5] Fix overlayfs on EVM
- From: Ignaz Forster <iforster@xxxxxxxx>
Re: possible deadlock in pipe_lock (2)
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: possible deadlock in pipe_lock (2)
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: possible deadlock in pipe_lock (2)
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: possible deadlock in pipe_lock (2)
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: possible deadlock in pipe_lock (2)
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: possible deadlock in pipe_lock (2)
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: possible deadlock in pipe_lock (2)
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [RFC][PATCH v2 0/5] Experiments with overlayfs filemap
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
[PATCH] fstests: Check that high-offset reads and writes work on non-blockdev fs
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [RFC][PATCH v2 0/5] Experiments with overlayfs filemap
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [RFC][PATCH v2 0/5] Experiments with overlayfs filemap
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [RFC][PATCH v2 0/5] Experiments with overlayfs filemap
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] xfstest, overlayfs: Use falloc to make sure a meta copy file got copied up
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH][v3] overlayfs: Do not lose security.capability xattr over metadata file copy-up
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
[PATCH] xfstest, overlayfs: Use falloc to make sure a meta copy file got copied up
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: [PATCH][v3] overlayfs: Do not lose security.capability xattr over metadata file copy-up
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: Failure to execute file on overlayfs during switch_root/chroot
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: Failure to execute file on overlayfs during switch_root/chroot
- From: aszlig <aszlig@nix.build>
Re: Failure to execute file on overlayfs during switch_root/chroot
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: Failure to execute file on overlayfs during switch_root/chroot
- From: aszlig <aszlig@nix.build>
Re: [RFC][PATCH v2 0/5] Experiments with overlayfs filemap
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [RFC][PATCH v2 0/5] Experiments with overlayfs filemap
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: [RFC][PATCH v2 0/5] Experiments with overlayfs filemap
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: [RFC][PATCH v2 0/5] Experiments with overlayfs filemap
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [RFC][PATCH v2 0/5] Experiments with overlayfs filemap
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [RFC][PATCH v2 0/5] Experiments with overlayfs filemap
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [RFC][PATCH v2 0/5] Experiments with overlayfs filemap
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [RFC][PATCH v2 0/5] Experiments with overlayfs filemap
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [RFC][PATCH v2 0/5] Experiments with overlayfs filemap
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [PATCH][v3] overlayfs: Do not lose security.capability xattr over metadata file copy-up
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH][v2] xfstests: overlay: Do not lose security.capability xattr over metadata only file copy-up
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH][v3] overlayfs: Do not lose security.capability xattr over metadata file copy-up
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
[PATCH][v2] xfstests: overlay: Do not lose security.capability xattr over metadata only file copy-up
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: [PATCH][V2] overlayfs: Do not lose security.capability xattr over metadata file copy-up
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] xfstests: overlay: Do not lose security.capability xattr over metadata only file copy-up
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH] xfstests: overlay: Do not lose security.capability xattr over metadata only file copy-up
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
[PATCH][V2] overlayfs: Do not lose security.capability xattr over metadata file copy-up
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: [PATCH] overlayfs: Do not lose security.capability xattr over metadata file copy-up
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
[PATCH] overlayfs: Do not lose security.capability xattr over metadata file copy-up
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: [RFC][PATCH v2 0/5] Experiments with overlayfs filemap
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [RFC][PATCH v2 0/5] Experiments with overlayfs filemap
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [RFC][PATCH v2 0/5] Experiments with overlayfs filemap
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [RFC][PATCH v2 0/5] Experiments with overlayfs filemap
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [RFC][PATCH v2 0/5] Experiments with overlayfs filemap
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [RFC][PATCH v2 0/5] Experiments with overlayfs filemap
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [RFC][PATCH v2 0/5] Experiments with overlayfs filemap
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [RFC][PATCH v2 0/5] Experiments with overlayfs filemap
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [RFC][PATCH v2 0/5] Experiments with overlayfs filemap
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [RFC][PATCH v2 0/5] Experiments with overlayfs filemap
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [RFC][PATCH v2 0/5] Experiments with overlayfs filemap
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: [RFC][PATCH v2 0/5] Experiments with overlayfs filemap
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH] overlay/061: enhance mmap ro/rw inconsistencies test
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [RFC][PATCH v2 0/5] Experiments with overlayfs filemap
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [RFC][PATCH v2 0/5] Experiments with overlayfs filemap
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [RFC][PATCH v2 0/5] Experiments with overlayfs filemap
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [RFC][PATCH v2 0/5] Experiments with overlayfs filemap
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [RFC][PATCH v2 0/5] Experiments with overlayfs filemap
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [RFC][PATCH v2 0/5] Experiments with overlayfs filemap
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [RFC][PATCH v2 0/5] Experiments with overlayfs filemap
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [RFC][PATCH v2 0/5] Experiments with overlayfs filemap
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [RFC][PATCH v2 0/5] Experiments with overlayfs filemap
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH v3] ima: define ima_post_create_tmpfile() hook and add missing call
- From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
Re: [PATCH] ovl: fix missing upper fs freeze protection on copy up for ioctl
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: [PATCH] ovl: fix missing upper fs freeze protection on copy up for ioctl
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] ovl: fix missing upper fs freeze protection on copy up for ioctl
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
[RFC][PATCH v2 5/5] ovl: noop aops to test filemap operations and lazy copy up
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[RFC][PATCH v2 4/5] ovl: lazy copy up data on page fault
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[RFC][PATCH v2 3/5] ovl: lazy copy up of data on first data access
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[RFC][PATCH v2 2/5] ovl: prepare for generic filemap file operations
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[RFC][PATCH v2 1/5] ovl: reorder tests in ovl_open_need_copy_up()
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[RFC][PATCH v2 0/5] Experiments with overlayfs filemap
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH] ovl: fix missing upper fs freeze protection on copy up for ioctl
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [RFC][PATCH] ovl: lazy copy up of data on first write
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [RFC][PATCH] ovl: lazy copy up of data on first write
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [RFC][PATCH] ovl: lazy copy up of data on first write
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: [RFC][PATCH] ovl: lazy copy up of data on first write
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: [RFC][PATCH] ovl: lazy copy up of data on first write
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [RFC][PATCH] ovl: lazy copy up of data on first write
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: Postpone copy-up until first real write?
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[RFC][PATCH] ovl: lazy copy up of data on first write
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] ovl: IMA Call ima_post_mknod_path() on copy_up'd dentry
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] ovl: IMA Call ima_post_mknod_path() on copy_up'd dentry
- From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
Re: [PATCH] ovl: IMA Call ima_post_mknod_path() on copy_up'd dentry
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH][V3] xfstest: overlay: File capabilities should not be lost over copy-up
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
[PATCH] ovl: IMA Call ima_post_mknod_path() on copy_up'd dentry
- From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
Re: [PATCH][V3] overlayfs: During copy up, first copy up data and then xattrs
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: Postpone copy-up until first real write?
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [PATCH][V2] xfstest: overlay: File capabilities should not be lost over copy-up
- From: Dave Chinner <david@xxxxxxxxxxxxx>
Re: Postpone copy-up until first real write?
- From: cgxu519 <cgxu519@xxxxxxx>
Re: Postpone copy-up until first real write?
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH][V2] xfstest: overlay: File capabilities should not be lost over copy-up
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
[PATCH][V3] overlayfs: During copy up, first copy up data and then xattrs
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: [PATCH] xfstest: overlay: File capabilities should not be lost over copy-up
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: [PATCH][V2] overlayfs: During copy up, first copy up data and then xattrs
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: [PATCH v2 0/3] Enable new features for nested overlayfs setups
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] xfstest: overlay: File capabilities should not be lost over copy-up
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH][V2] overlayfs: During copy up, first copy up data and then xattrs
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH] xfstest: overlay: File capabilities should not be lost over copy-up
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
[PATCH][V2] overlayfs: During copy up, first copy up data and then xattrs
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: [PATCH] overlayfs: During copy up, first copy up data and then xattrs
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: EVM: Permission denied with overlayfs
- From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
Re: [Fwd: Re: EVM: Permission denied with overlayfs]
- From: Mimi Zohar <zohar@xxxxxxxxxxxxx>
Re: [Fwd: Re: EVM: Permission denied with overlayfs]
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: EVM: Permission denied with overlayfs
- From: Mimi Zohar <zohar@xxxxxxxxxxxxx>
Re: [Fwd: Re: EVM: Permission denied with overlayfs]
- From: Mimi Zohar <zohar@xxxxxxxxxxxxx>
Re: [Fwd: Re: EVM: Permission denied with overlayfs]
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [Fwd: Re: EVM: Permission denied with overlayfs]
- From: Mimi Zohar <zohar@xxxxxxxxxxxxx>
Re: EVM: Permission denied with overlayfs
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: EVM: Permission denied with overlayfs
- From: Goldwyn Rodrigues <rgoldwyn@xxxxxxxx>
Re: EVM: Permission denied with overlayfs
- From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
Re: EVM: Permission denied with overlayfs
- From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
Re: EVM: Permission denied with overlayfs
- From: Mimi Zohar <zohar@xxxxxxxxxxxxx>
Re: [Fwd: Re: EVM: Permission denied with overlayfs]
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: EVM: Permission denied with overlayfs
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: EVM: Permission denied with overlayfs
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] overlayfs: During copy up, first copy up data and then xattrs
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: EVM: Permission denied with overlayfs
- From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
[PATCH] overlayfs: During copy up, first copy up data and then xattrs
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: EVM: Permission denied with overlayfs
- From: Mimi Zohar <zohar@xxxxxxxxxxxxx>
Re: EVM: Permission denied with overlayfs
- From: Mimi Zohar <zohar@xxxxxxxxxxxxx>
Re: EVM: Permission denied with overlayfs
- From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
Re: EVM: Permission denied with overlayfs
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: EVM: Permission denied with overlayfs
- From: Mimi Zohar <zohar@xxxxxxxxxxxxx>
Re: EVM: Permission denied with overlayfs
- From: Mimi Zohar <zohar@xxxxxxxxxxxxx>
EVM: Permission denied with overlayfs
- From: Ignaz Forster <iforster@xxxxxxx>
Re: WARNING in ovl_instantiate
- From: Dmitry Vyukov <dvyukov@xxxxxxxxxx>
Re: [PATCH v5] syscalls/readahead02: test readahead using posix_fadvise()
- From: Cyril Hrubis <chrubis@xxxxxxx>
Re: WARNING in ovl_instantiate
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: WARNING in ovl_instantiate
- From: Dmitry Vyukov <dvyukov@xxxxxxxxxx>
Re: WARNING in ovl_instantiate
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: WARNING in ovl_instantiate
- From: syzbot <syzbot+9c69c282adc4edd2b540@xxxxxxxxxxxxxxxxxxxxxxxxx>
Re: [PATCH v5] syscalls/readahead02: test readahead using posix_fadvise()
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [EXTERNAL] Re: Copy_up function fail with ubifs on upper layer
- From: Richard Weinberger <richard@xxxxxx>
Re: [GIT PULL] overlayfs fixes for 4.20-rc7
- From: pr-tracker-bot@xxxxxxxxxx
Re: overlayfs access checks on underlying layers
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Stephen Smalley <sds@xxxxxxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Stephen Smalley <sds@xxxxxxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: [PATCH] fs: Evaluate O_WRONLY | O_RDWR to O_RDWR
- From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
Re: [PATCH] fs: Evaluate O_WRONLY | O_RDWR to O_RDWR
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
Re: [PATCH] fs: Evaluate O_WRONLY | O_RDWR to O_RDWR
- From: Dmitry Vyukov <dvyukov@xxxxxxxxxx>
Re: [PATCH] fs: Evaluate O_WRONLY | O_RDWR to O_RDWR
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] fs: Evaluate O_WRONLY | O_RDWR to O_RDWR
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
[PATCH] fs: Evaluate O_WRONLY | O_RDWR to O_RDWR
- From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
Re: [PATCH 04/11] vfs: add missing checks to copy_file_range
- From: Luis Henriques <lhenriques@xxxxxxxx>
Re: [PATCH 04/11] vfs: add missing checks to copy_file_range
- From: Olga Kornievskaia <olga.kornievskaia@xxxxxxxxx>
Re: [PATCH 04/11] vfs: add missing checks to copy_file_range
- From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
Re: [PATCH 04/11] vfs: add missing checks to copy_file_range
- From: Olga Kornievskaia <olga.kornievskaia@xxxxxxxxx>
Re: [PATCH 04/11] vfs: add missing checks to copy_file_range
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Stephen Smalley <sds@xxxxxxxxxxxxx>
Re: [PATCH 04/11] vfs: add missing checks to copy_file_range
- From: Luis Henriques <lhenriques@xxxxxxxx>
[GIT PULL] overlayfs fixes for 4.20-rc7
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Paul Moore <paul@xxxxxxxxxxxxxx>
RE: [EXTERNAL] Re: Copy_up function fail with ubifs on upper layer
- From: "Guerard, Vincent" <VincentGuerard@xxxxxxxxx>
Re: [EXTERNAL] Re: Copy_up function fail with ubifs on upper layer
- From: Richard Weinberger <richard@xxxxxx>
Re: [EXTERNAL] Re: Copy_up function fail with ubifs on upper layer
- From: Amir Goldstein <amir73il@xxxxxxxxx>
RE: [EXTERNAL] Re: Copy_up function fail with ubifs on upper layer
- From: "Guerard, Vincent" <VincentGuerard@xxxxxxxxx>
Re: [PATCH 03/11] vfs: no fallback for ->copy_file_range
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH 03/11] vfs: no fallback for ->copy_file_range
- From: Dave Chinner <david@xxxxxxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Stephen Smalley <sds@xxxxxxxxxxxxx>
Re: [PATCH 03/11] vfs: no fallback for ->copy_file_range
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH 01/11] vfs: copy_file_range source range over EOF should fail
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Re: [PATCH 01/11] vfs: copy_file_range source range over EOF should fail
- From: Dave Chinner <david@xxxxxxxxxxxxx>
Re: [PATCH 05/11] vfs: use inode_permission in copy_file_range()
- From: bfields@xxxxxxxxxxxx (J. Bruce Fields)
Re: [PATCH 09/11] vfs: push copy_file_ranges -EXDEV checks down
- From: Olga Kornievskaia <olga.kornievskaia@xxxxxxxxx>
Re: [PATCH 01/11] vfs: copy_file_range source range over EOF should fail
- From: bfields@xxxxxxxxxxxx (J. Bruce Fields)
Re: [PATCH 01/11] vfs: copy_file_range source range over EOF should fail
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Re: [PATCH 09/11] vfs: push copy_file_ranges -EXDEV checks down
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: [PATCH 09/11] vfs: push copy_file_ranges -EXDEV checks down
- From: Olga Kornievskaia <olga.kornievskaia@xxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Paul Moore <paul@xxxxxxxxxxxxxx>
Re: [PATCH 01/11] vfs: copy_file_range source range over EOF should fail
- From: Dave Chinner <david@xxxxxxxxxxxxx>
Re: [PATCH 09/11] vfs: push copy_file_ranges -EXDEV checks down
- From: Dave Chinner <david@xxxxxxxxxxxxx>
Re: [PATCH 01/11] vfs: copy_file_range source range over EOF should fail
- From: Olga Kornievskaia <olga.kornievskaia@xxxxxxxxx>
Re: [PATCH 01/11] vfs: copy_file_range source range over EOF should fail
- From: Dave Chinner <david@xxxxxxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Stephen Smalley <sds@xxxxxxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Stephen Smalley <sds@xxxxxxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Stephen Smalley <sds@xxxxxxxxxxxxx>
Re: [PATCH 09/11] vfs: push copy_file_ranges -EXDEV checks down
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Stephen Smalley <sds@xxxxxxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
[PATCH v5] syscalls/readahead02: test readahead using posix_fadvise()
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [PATCH 07/11] vfs: copy_file_range should update file timestamps
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: [PATCH 06/11] vfs: copy_file_range needs to strip setuid bits
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Re: [PATCH 05/11] vfs: use inode_permission in copy_file_range()
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Re: [PATCH 04/11] vfs: add missing checks to copy_file_range
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Re: [PATCH 03/11] vfs: no fallback for ->copy_file_range
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: [PATCH 02/11] vfs: introduce generic_copy_file_range()
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Re: [PATCH 01/11] vfs: copy_file_range source range over EOF should fail
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Stephen Smalley <sds@xxxxxxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Stephen Smalley <sds@xxxxxxxxxxxxx>
Re: [PATCH v4 6/6] syscalls/readahead02: test readahead using posix_fadvise()
- From: Cyril Hrubis <chrubis@xxxxxxx>
Re: [PATCH v4 5/6] syscalls/readahead02: test readahead() on an overlayfs file
- From: Cyril Hrubis <chrubis@xxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [PATCH 08/11] vfs: push EXDEV check down into ->remap_file_range
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH 08/11] vfs: push EXDEV check down into ->remap_file_range
- From: Olga Kornievskaia <olga.kornievskaia@xxxxxxxxx>
Re: [PATCH 08/11] vfs: push EXDEV check down into ->remap_file_range
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
Re: [PATCH 05/11] vfs: use inode_permission in copy_file_range()
- From: Dave Chinner <david@xxxxxxxxxxxxx>
Re: [PATCH 09/11] vfs: push copy_file_ranges -EXDEV checks down
- From: Dave Chinner <david@xxxxxxxxxxxxx>
Re: [PATCH 08/11] vfs: push EXDEV check down into ->remap_file_range
- From: Dave Chinner <david@xxxxxxxxxxxxx>
Re: [PATCH 08/11] vfs: push EXDEV check down into ->remap_file_range
- From: Dave Chinner <david@xxxxxxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Paul Moore <paul@xxxxxxxxxxxxxx>
Re: [PATCH 07/11] vfs: copy_file_range should update file timestamps
- From: Dave Chinner <david@xxxxxxxxxxxxx>
Re: [PATCH 04/11] vfs: add missing checks to copy_file_range
- From: Dave Chinner <david@xxxxxxxxxxxxx>
Re: [PATCH 03/11] vfs: no fallback for ->copy_file_range
- From: Dave Chinner <david@xxxxxxxxxxxxx>
Re: [PATCH 02/11] vfs: introduce generic_copy_file_range()
- From: Dave Chinner <david@xxxxxxxxxxxxx>
Re: [PATCH 04/11] vfs: add missing checks to copy_file_range
- From: Olga Kornievskaia <olga.kornievskaia@xxxxxxxxx>
Re: [PATCH 09/11] vfs: push copy_file_ranges -EXDEV checks down
- From: Olga Kornievskaia <olga.kornievskaia@xxxxxxxxx>
Re: [PATCH 08/11] vfs: push EXDEV check down into ->remap_file_range
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
Re: [PATCH 04/11] vfs: add missing checks to copy_file_range
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
Re: [PATCH 09/11] vfs: push copy_file_ranges -EXDEV checks down
- From: Anna Schumaker <schumaker.anna@xxxxxxxxx>
Re: [PATCH 05/11] vfs: use inode_permission in copy_file_range()
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
Re: [PATCH 08/11] vfs: push EXDEV check down into ->remap_file_range
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
Re: [PATCH 03/11] vfs: no fallback for ->copy_file_range
- From: Anna Schumaker <schumaker.anna@xxxxxxxxx>
Re: [PATCH 07/11] vfs: copy_file_range should update file timestamps
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
Re: [PATCH 05/11] vfs: use inode_permission in copy_file_range()
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
Re: [PATCH 09/11] vfs: push copy_file_ranges -EXDEV checks down
- From: Olga Kornievskaia <olga.kornievskaia@xxxxxxxxx>
Re: [PATCH 07/11] vfs: copy_file_range should update file timestamps
- From: Olga Kornievskaia <olga.kornievskaia@xxxxxxxxx>
Re: [PATCH v4 1/6] syscalls/readahead02: Convert to newlib and cleanup
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH v4 2/6] syscalls/readahead02: abort test if readahead syscall fails
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH v4 1/6] syscalls/readahead02: Convert to newlib and cleanup
- From: Cyril Hrubis <chrubis@xxxxxxx>
Re: [PATCH v4 2/6] syscalls/readahead02: abort test if readahead syscall fails
- From: Cyril Hrubis <chrubis@xxxxxxx>
Re: [PATCH 12/11] man-pages: copy_file_range updates
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH 11/11] ovl: allow cross-device copy_file_range calls
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH 10/11] vfs: allow generic_copy_file_range to copy across devices
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH 06/11] vfs: copy_file_range needs to strip setuid bits
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH 05/11] vfs: use inode_permission in copy_file_range()
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH 01/11] vfs: copy_file_range source range over EOF should fail
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH 04/11] vfs: add missing checks to copy_file_range
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH 09/11] vfs: push copy_file_ranges -EXDEV checks down
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH 08/11] vfs: push EXDEV check down into ->remap_file_range
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH 07/11] vfs: copy_file_range should update file timestamps
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH 03/11] vfs: no fallback for ->copy_file_range
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH 02/11] vfs: introduce generic_copy_file_range()
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH 12/11] man-pages: copy_file_range updates
- From: Dave Chinner <david@xxxxxxxxxxxxx>
[PATCH 04/11] vfs: add missing checks to copy_file_range
- From: Dave Chinner <david@xxxxxxxxxxxxx>
[PATCH 09/11] vfs: push copy_file_ranges -EXDEV checks down
- From: Dave Chinner <david@xxxxxxxxxxxxx>
[PATCH 05/11] vfs: use inode_permission in copy_file_range()
- From: Dave Chinner <david@xxxxxxxxxxxxx>
[PATCH 10/11] vfs: allow generic_copy_file_range to copy across devices
- From: Dave Chinner <david@xxxxxxxxxxxxx>
[PATCH 11/11] ovl: allow cross-device copy_file_range calls
- From: Dave Chinner <david@xxxxxxxxxxxxx>
[PATCH 08/11] vfs: push EXDEV check down into ->remap_file_range
- From: Dave Chinner <david@xxxxxxxxxxxxx>
[PATCH 07/11] vfs: copy_file_range should update file timestamps
- From: Dave Chinner <david@xxxxxxxxxxxxx>
[PATCH 06/11] vfs: copy_file_range needs to strip setuid bits
- From: Dave Chinner <david@xxxxxxxxxxxxx>
[PATCH 03/11] vfs: no fallback for ->copy_file_range
- From: Dave Chinner <david@xxxxxxxxxxxxx>
[PATCH 02/11] vfs: introduce generic_copy_file_range()
- From: Dave Chinner <david@xxxxxxxxxxxxx>
[PATCH 0/11] fs: fixes for major copy_file_range() issues
- From: Dave Chinner <david@xxxxxxxxxxxxx>
[PATCH 01/11] vfs: copy_file_range source range over EOF should fail
- From: Dave Chinner <david@xxxxxxxxxxxxx>
Re: [PATCH v2 2/2] iomap: partially revert 4721a601099 (simulated directio short read on EFAULT)
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH v2 2/2] iomap: partially revert 4721a601099 (simulated directio short read on EFAULT)
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
[PATCH v2 1/2] splice: don't read more than available pipe space
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
Re: [RFC PATCH] splice: don't read more than available pipe space
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Re: [PATCH] vfs: allow remap flags to be passed to vfs_clone_file_range
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
[PATCH v2] vfs: allow some remap flags to be passed to vfs_clone_file_range
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
Re: [RFC PATCH] splice: don't read more than available pipe space
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] vfs: allow remap flags to be passed to vfs_clone_file_range
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [4.20-rc4 regression] generic/095 Concurrent mixed I/O hang on xfs based overlayfs
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH] vfs: allow remap flags to be passed to vfs_clone_file_range
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
[RFC PATCH] splice: don't read more than available pipe space
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
Re: [4.20-rc4 regression] generic/095 Concurrent mixed I/O hang on xfs based overlayfs
- From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
Re: [4.20-rc4 regression] generic/095 Concurrent mixed I/O hang on xfs based overlayfs
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [4.20-rc4 regression] generic/095 Concurrent mixed I/O hang on xfs based overlayfs
- From: Zorro Lang <zlang@xxxxxxxxxx>
[4.20-rc4 regression] generic/095 Concurrent mixed I/O hang on xfs based overlayfs
- From: Murphy Zhou <jencce.kernel@xxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Daniel Walsh <dwalsh@xxxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Stephen Smalley <sds@xxxxxxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Stephen Smalley <sds@xxxxxxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Stephen Smalley <sds@xxxxxxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Stephen Smalley <sds@xxxxxxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Stephen Smalley <sds@xxxxxxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Stephen Smalley <sds@xxxxxxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: [PATCH v3 2/6] syscalls/readahead02: Convert to newlib and cleanup
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH v4 6/6] syscalls/readahead02: test readahead using posix_fadvise()
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH v4 5/6] syscalls/readahead02: test readahead() on an overlayfs file
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH v4 4/6] syscalls/readahead02: Convert to tst_timer helpers
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH v4 3/6] syscalls/readahead02: fail test if readahead did not use any cache
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH v4 1/6] syscalls/readahead02: Convert to newlib and cleanup
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH v4 2/6] syscalls/readahead02: abort test if readahead syscall fails
- From: Amir Goldstein <amir73il@xxxxxxxxx>
[PATCH v4 0/6] Tests for readahead() and fadvise() on overlayfs
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: [PATCH v3 3/6] syscalls/readahead02: abort test if readahead syscall fails
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Re: overlayfs access checks on underlying layers
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
overlayfs access checks on underlying layers
- From: Miklos Szeredi <miklos@xxxxxxxxxx>
Re: possible deadlock in ovl_write_iter
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: possible deadlock in ovl_write_iter
- From: Dmitry Vyukov <dvyukov@xxxxxxxxxx>
Re: possible deadlock in ovl_write_iter
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] IMA: Mask O_RDWR if FMODE_READ is set
- From: Dmitry Vyukov <dvyukov@xxxxxxxxxx>
Re: possible deadlock in ovl_write_iter
- From: Dmitry Vyukov <dvyukov@xxxxxxxxxx>
Re: [PATCH] IMA: Mask O_RDWR if FMODE_READ is set
- From: Amir Goldstein <amir73il@xxxxxxxxx>
Re: [PATCH] IMA: Mask O_RDWR if FMODE_READ is set
- From: Mimi Zohar <zohar@xxxxxxxxxxxxx>
Re: possible deadlock in ovl_write_iter
- From: Amir Goldstein <amir73il@xxxxxxxxx>

[Index of Archives] [Linux Filesystems Devel] [Linux NFS] [Linux NILFS] [Linux USB Devel] [Linux Audio Users] [Yosemite News] [Linux Kernel] [Linux SCSI]