messages from 2018-12-03 12:52:59 to 2019-01-30 15:53:04 UTC [more...]
[PATCH][V2] overlayfs: Do not lose security.capability xattr over metadata file copy-up
2019-01-30 15:53 UTC
[PATCH] overlayfs: Do not lose security.capability xattr over metadata file copy-up
2019-01-30 15:43 UTC (2+ messages)
Failure to execute file on overlayfs during switch_root/chroot
2019-01-29 19:41 UTC
[RFC][PATCH v2 0/5] Experiments with overlayfs filemap
2019-01-29 16:47 UTC (27+ messages)
` [RFC][PATCH v2 1/5] ovl: reorder tests in ovl_open_need_copy_up()
` [RFC][PATCH v2 2/5] ovl: prepare for generic filemap file operations
` [RFC][PATCH v2 3/5] ovl: lazy copy up of data on first data access
` [RFC][PATCH v2 4/5] ovl: lazy copy up data on page fault
` [RFC][PATCH v2 5/5] ovl: noop aops to test filemap operations and lazy copy up
[PATCH] overlay/061: enhance mmap ro/rw inconsistencies test
2019-01-27 8:38 UTC
[PATCH v3] ima: define ima_post_create_tmpfile() hook and add missing call
2019-01-22 20:06 UTC
[PATCH] ovl: fix missing upper fs freeze protection on copy up for ioctl
2019-01-22 18:47 UTC (4+ messages)
[RFC][PATCH] ovl: lazy copy up of data on first write
2019-01-18 20:12 UTC (7+ messages)
Postpone copy-up until first real write?
2019-01-18 13:52 UTC (7+ messages)
[PATCH] ovl: IMA Call ima_post_mknod_path() on copy_up'd dentry
2019-01-17 15:44 UTC (4+ messages)
[PATCH][V3] xfstest: overlay: File capabilities should not be lost over copy-up
2019-01-16 21:04 UTC
[PATCH][V3] overlayfs: During copy up, first copy up data and then xattrs
2019-01-15 9:26 UTC (2+ messages)
[PATCH][V2] xfstest: overlay: File capabilities should not be lost over copy-up
2019-01-15 3:57 UTC (2+ messages)
[PATCH] xfstest: overlay: File capabilities should not be lost over copy-up
2019-01-11 18:36 UTC (3+ messages)
[PATCH][V2] overlayfs: During copy up, first copy up data and then xattrs
2019-01-11 18:35 UTC (3+ messages)
[PATCH v2 0/3] Enable new features for nested overlayfs setups
2019-01-11 6:37 UTC (2+ messages)
[PATCH] overlayfs: During copy up, first copy up data and then xattrs
2018-12-26 19:09 UTC (3+ messages)
EVM: Permission denied with overlayfs
2018-12-20 19:24 UTC (23+ messages)
` [Fwd: Re: EVM: Permission denied with overlayfs]
WARNING in ovl_instantiate
2018-12-18 14:12 UTC (6+ messages)
[PATCH v5] syscalls/readahead02: test readahead using posix_fadvise()
2018-12-18 13:01 UTC (3+ messages)
[EXTERNAL] Re: Copy_up function fail with ubifs on upper layer
2018-12-13 21:25 UTC (5+ messages)
[GIT PULL] overlayfs fixes for 4.20-rc7
2018-12-13 21:15 UTC (2+ messages)
overlayfs access checks on underlying layers
2018-12-13 20:26 UTC (41+ messages)
[PATCH] fs: Evaluate O_WRONLY | O_RDWR to O_RDWR
2018-12-13 14:05 UTC (6+ messages)
[PATCH 0/11] fs: fixes for major copy_file_range() issues
2018-12-13 10:29 UTC (74+ messages)
` [PATCH 01/11] vfs: copy_file_range source range over EOF should fail
` [PATCH 02/11] vfs: introduce generic_copy_file_range()
` [PATCH 03/11] vfs: no fallback for ->copy_file_range
` [PATCH 04/11] vfs: add missing checks to copy_file_range
` [PATCH 05/11] vfs: use inode_permission in copy_file_range()
` [PATCH 06/11] vfs: copy_file_range needs to strip setuid bits
` [PATCH 07/11] vfs: copy_file_range should update file timestamps
` [PATCH 08/11] vfs: push EXDEV check down into ->remap_file_range
` [PATCH 09/11] vfs: push copy_file_ranges -EXDEV checks down
` [PATCH 10/11] vfs: allow generic_copy_file_range to copy across devices
` [PATCH 11/11] ovl: allow cross-device copy_file_range calls
` [PATCH 12/11] man-pages: copy_file_range updates
[PATCH v4 0/6] Tests for readahead() and fadvise() on overlayfs
2018-12-04 14:10 UTC (11+ messages)
` [PATCH v4 1/6] syscalls/readahead02: Convert to newlib and cleanup
` [PATCH v4 2/6] syscalls/readahead02: abort test if readahead syscall fails
` [PATCH v4 5/6] syscalls/readahead02: test readahead() on an overlayfs file
` [PATCH v4 6/6] syscalls/readahead02: test readahead using posix_fadvise()
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox