messages from 2016-09-06 11:59:45 to 2016-10-31 13:51:50 UTC [more...]
ACL test failures on overlayfs over tmpfs
2016-10-31 13:51 UTC (3+ messages)
` Fwd: "
[PATCH 0/3] overlayfs: allow moving directory trees
2016-10-30 22:00 UTC (20+ messages)
` [PATCH 1/3] ovl: check fs features
` [PATCH 2/3] vfs: export vfs_path_lookup()
` [PATCH 3/3] ovl: redirect on rename-dir
` [PATCH] ovl: check for emptiness of redirect dir
[PATCH] ovl: update S_ISGID when setting posix ACLs
2016-10-28 19:22 UTC (8+ messages)
` [PATCH v2] "
[PATCH] vfs: fix vfs_clone_file_range() for overlayfs files
2016-10-28 15:25 UTC (3+ messages)
[POC/RFC PATCH] overlayfs: fix data inconsistency at copy up
2016-10-24 8:11 UTC (14+ messages)
[PATCH 07/12] vfs: do get_write_access() on upper layer of overlayfs
2016-10-19 8:56 UTC (6+ messages)
[PATCH 1/3] t_truncate_self: describe self better in error message
2016-10-19 8:52 UTC (3+ messages)
` [PATCH 2/3] overlay/013: fix bug in test_upper creation
` [PATCH 3/3] overlay/013: adjust test expectation to kernel v4.8
Problem with parcel shipping, ID:00000901336
2016-10-15 14:19 UTC
[GIT PULL] overlayfs update for 4.9
2016-10-14 10:10 UTC (6+ messages)
[GIT PULL (updated)] overlayfs update for 4.9
2016-10-14 9:39 UTC
Problems with item delivery, n.0000656601
2016-10-12 23:43 UTC
Exporting overlay via NFS?
2016-10-12 18:40 UTC (2+ messages)
[GIT PULL] overlayfs update for 4.9
2016-10-11 19:49 UTC (5+ messages)
Operation not permitted when removing file in stacked overlayfs
2016-10-11 13:34 UTC
[PATCH v6 00/16] Xattr inode operation removal
2016-10-06 21:34 UTC (21+ messages)
` [PATCH v6 01/16] xattr: Remove unnecessary NULL attribute name check
` [PATCH v6 02/16] jffs2: Remove jffs2_{get,set,remove}xattr macros
` [PATCH v6 03/16] hfs: Switch to generic xattr handlers
` [PATCH v6 04/16] kernfs: "
` [PATCH v6 05/16] sockfs: getxattr: Fail with -EOPNOTSUPP for invalid attribute names
` [PATCH v6 06/16] sockfs: Get rid of getxattr iop
` [PATCH v6 07/16] ecryptfs: Switch to generic xattr handlers
` [PATCH v6 08/16] lustre: "
` [PATCH v6 09/16] vfs: Move xattr_resolve_name to the front of fs/xattr.c
` [PATCH v6 10/16] vfs: Add IOP_XATTR inode operations flag
` [PATCH v6 11/16] vfs: Use IOP_XATTR flag for bad-inode handling
` [PATCH v6 12/16] libfs: Use IOP_XATTR flag for empty directory handling
` [PATCH v6 13/16] xattr: Add __vfs_{get,set,remove}xattr helpers
` [PATCH v6 14/16] vfs: Check for the IOP_XATTR flag in listxattr
` [PATCH v6 15/16] xattr: Stop calling {get,set,remove}xattr inode operations
` [PATCH v6 16/16] vfs: Remove "
[PATCH v3 0/4] ovl: efficient copy up by reflink
2016-09-30 11:14 UTC (28+ messages)
` [PATCH v3 1/4] vfs: allow vfs_clone_file_range() across mount points
` [PATCH v3 2/4] ovl: use vfs_clone_file_range() for copy up if possible
` [PATCH v3 3/4] vfs: allow vfs_copy_file_range() across file systems
` [PATCH v3 4/4] ovl: use vfs_copy_file_range() to copy up file data
[PATCH v5 00/17] Xattr inode operation removal
2016-09-28 22:40 UTC (19+ messages)
` [PATCH v5 01/17] xattr: Remove unnecessary NULL attribute name check
` [PATCH v5 02/17] jffs2: Remove jffs2_{get,set,remove}xattr macros
` [PATCH v5 03/17] hfs: Switch to generic xattr handlers
` [PATCH v5 04/17] kernfs: "
` [PATCH v5 05/17] sockfs: getxattr: Fail with -EOPNOTSUPP for invalid attribute names
` [PATCH v5 06/17] sockfs: Get rid of getxattr iop
` [PATCH v5 07/17] ecryptfs: Switch to generic xattr handlers
` [PATCH v5 08/17] fuse: "
` [PATCH v5 09/17] lustre: "
` [PATCH v5 10/17] vfs: Move xattr_resolve_name to the front of fs/xattr.c
` [PATCH v5 11/17] vfs: Add IOP_XATTR inode operations flag
` [PATCH v5 12/17] vfs: Use IOP_XATTR flag for bad-inode handling
` [PATCH v5 13/17] libfs: Use IOP_XATTR flag for empty directory handling
` [PATCH v5 14/17] xattr: Add __vfs_{get,set,remove}xattr helpers
` [PATCH v5 15/17] vfs: Check for the IOP_XATTR flag in listxattr
` [PATCH v5 16/17] xattr: Stop calling {get,set,remove}xattr inode operations
` [PATCH v5 17/17] vfs: Remove "
[PATCH v4 0/4] ovl: efficient copy up by reflink
2016-09-26 18:17 UTC (5+ messages)
` [PATCH v4 1/3] vfs: allow vfs_clone_file_range() across mount points
` [PATCH v4 2/3] vfs: call vfs_clone_file_range() under mnt_want_write()
` [PATCH v4 3/3] ovl: use vfs_clone_file_range() for copy up if possible
Hi, Is this a problem?
2016-09-23 8:16 UTC (2+ messages)
[PATCH] ovl: Fix info leak in ovl_lookup_temp()
2016-09-21 14:38 UTC (3+ messages)
overlayfs: EOPNOTSUPP when writing in overlayfs with nfs4 as lower dir
2016-09-20 13:45 UTC
running binaries under doubly stacked overlayfs
2016-09-20 8:52 UTC (2+ messages)
[PATCH] ovl: avoid setting uninitialized creds
2016-09-19 14:53 UTC (2+ messages)
[PATCH] ovl: use copy_file_range for copy up if possible
2016-09-14 12:43 UTC (24+ messages)
` [PATCH v2 0/4] ovl: efficient copy up by reflink
` [PATCH v2 1/4] vfs: allow vfs_clone_file_range() across mount points
` [PATCH v2 2/4] ovl: use vfs_clone_file_range() for copy up if possible
` [PATCH v2 3/4] vfs: allow vfs_copy_file_range() across file systems
` [PATCH v2 4/4] ovl: use vfs_copy_file_range() to copy up file data
[miklos-vfs:readlink 16/17] ERROR: "vfs_get_link" [fs/overlayfs/overlay.ko] undefined!
2016-09-12 17:24 UTC
[miklos-vfs:readlink 17/17] ERROR: "vfs_get_link" [fs/ecryptfs/ecryptfs.ko] undefined!
2016-09-13 1:30 UTC
[PATCH v1] ovl: use copy_file_clone for copy up if possible
2016-09-11 10:50 UTC
[GIT PULL] overlayfs fix for 4.8-rc5
2016-09-09 21:47 UTC (6+ messages)
[PATCH] generic: simple permission check on hard links
2016-09-07 22:45 UTC (2+ messages)
overlayfs + ubifs: power cut results in "failed to create directory /overlay/work/work (errno: 17); mounting read-only"
2016-09-07 8:28 UTC (6+ messages)
[PATCH] overlayfs: During copy up, switch to mounter's creds early
2016-09-06 17:40 UTC
[PATCH] ovl: Fix for filesystems without POSIX ACL support
2016-09-06 12:47 UTC (2+ messages)
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