From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v3 0/2] btrfs-progs: make sure "mkfs --rootdir" copies all the attributes for the rootdir
Date: Thu, 12 Oct 2023 07:19:24 +1030 [thread overview]
Message-ID: <cover.1697057301.git.wqu@suse.com> (raw)
[CHANGELOG]
v3:
- Use 'stat()' instead pf 'lstate()' for the rootdir
This would follow a softlink for the rootdir.
v2:
- Add more attributes to be copied for rootdir, including:
* mode
* uid
* gid
* timestamps
- Update the test case
* Use two loopback devices
One to store the source directory, so that we're ensured to have
xattr support.
* Add checks for all the uid/gid/mode attributes
We got a bug report that "mkfs.btrfs --rootdir" copies all the xattr but
the xattr of the source directory.
It turns out that we only do the regular xattr/gid/uid/mode/timestamps
copy for all the child inodes, not the source directory itself.
Fix it and create a test case for it.
Qu Wenruo (2):
btrfs-progs: mkfs/rootdir: copy missing attributes for the rootdir
inode
btrfs-progs: tests/mkfs: make sure rootdir inode got its attributes
copied
mkfs/rootdir.c | 88 ++++++++++++++++------
tests/mkfs-tests/027-rootdir-inode/test.sh | 60 +++++++++++++++
2 files changed, 127 insertions(+), 21 deletions(-)
create mode 100755 tests/mkfs-tests/027-rootdir-inode/test.sh
--
2.42.0
next reply other threads:[~2023-10-11 20:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 20:49 Qu Wenruo [this message]
2023-10-11 20:49 ` [PATCH v3 1/2] btrfs-progs: mkfs/rootdir: copy missing attributes for the rootdir inode Qu Wenruo
2023-10-13 15:55 ` David Sterba
2023-10-13 19:55 ` Qu Wenruo
2023-10-17 17:23 ` David Sterba
2023-10-13 16:13 ` David Sterba
2023-10-11 20:49 ` [PATCH v3 2/2] btrfs-progs: tests/mkfs: make sure rootdir inode got its attributes copied Qu Wenruo
2023-10-13 16:21 ` [PATCH v3 0/2] btrfs-progs: make sure "mkfs --rootdir" copies all the attributes for the rootdir David Sterba
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=cover.1697057301.git.wqu@suse.com \
--to=wqu@suse.com \
--cc=linux-btrfs@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.