From: Amir Goldstein <amir73il@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Chengguang Xu <cgxu519@mykernel.net>, linux-unionfs@vger.kernel.org
Subject: [PATCH v2 0/3] Overlayfs fileattr related fixes
Date: Thu, 17 Jun 2021 18:22:38 +0300 [thread overview]
Message-ID: <20210617152241.987010-1-amir73il@gmail.com> (raw)
Miklos,
With these patches, copy up preserves the vfs aware subset of fileattr
flags, so xfstest overlay/075 passes.
I've tested also some generic chattr xfstests and written a new test
to verify the logic of overlay.xflags xattr [2].
Changes since v1 [1]:
- Store (i),(a) flags in xattr text format
- Copy up (A),(S) flags to upper fileattr
- Fixes the problems with setting ovl dirs and hardlinks immutable
[1] https://lore.kernel.org/linux-unionfs/CAJfpeguMQca-+vTdzoDdDWNJraWyqMa3vYRFDWPMk_R6-L7Obw@mail.gmail.com/
[2] https://github.com/amir73il/xfstests/commits/ovl-xflags
Amir Goldstein (3):
ovl: pass ovl_fs to ovl_check_setxattr()
ovl: copy up sync/noatime fileattr flags
ovl: consistent behavior for immutable/append-only inodes
fs/overlayfs/copy_up.c | 72 +++++++++++++---
fs/overlayfs/dir.c | 6 +-
fs/overlayfs/inode.c | 58 ++++++++++---
fs/overlayfs/namei.c | 2 +-
fs/overlayfs/overlayfs.h | 44 +++++++++-
fs/overlayfs/util.c | 178 ++++++++++++++++++++++++++++++++++++++-
6 files changed, 323 insertions(+), 37 deletions(-)
--
2.32.0
next reply other threads:[~2021-06-17 15:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 15:22 Amir Goldstein [this message]
2021-06-17 15:22 ` [PATCH v2 1/3] ovl: pass ovl_fs to ovl_check_setxattr() Amir Goldstein
2021-06-17 15:22 ` [PATCH v2 2/3] ovl: copy up sync/noatime fileattr flags Amir Goldstein
2021-06-17 15:22 ` [PATCH v2 3/3] ovl: consistent behavior for immutable/append-only inodes Amir Goldstein
2021-06-18 13:57 ` Miklos Szeredi
2021-06-18 15:54 ` Amir Goldstein
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210617152241.987010-1-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=cgxu519@mykernel.net \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).