From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/3] btrfs-progs: print-tree: cleanup for regular bitmap based flags print
Date: Fri, 4 Oct 2024 15:22:02 +0930 [thread overview]
Message-ID: <cover.1728020867.git.wqu@suse.com> (raw)
The first 2 are small cleanups for __print_readable_flag().
The last one introduces an sprint version, sprint_readable_flag(),
allowing the same bitmap handling of print_readable_flag() to be output
into a string buffer.
And use that sprint_readable_flag() to handle inode flags, inspired by a
recent report that Synology's out-of-tree btrfs can not be handled by
upstream kernel (unsupported inode flag).
This allows print-tree to handle the unknown flags of inode flags.
Unfortunately I didn't find any other location can benefit the
sprint_readable_flag() yet.
It's either bg flags which needs special handling for SINGLE profile, or
not bitmap in the first place (e.g. compress flags).
Qu Wenruo (3):
btrfs-progs: print-tree: use ARRAY_SIZE() to replace open-coded ones
btrfs-progs: print-tree: cleanup __print_readable_flag()
btrfs-progs: print-tree: use readable_flag_entry for inode flags
kernel-shared/print-tree.c | 128 +++++++++++++++++++++----------------
1 file changed, 72 insertions(+), 56 deletions(-)
--
2.46.2
next reply other threads:[~2024-10-04 5:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 5:52 Qu Wenruo [this message]
2024-10-04 5:52 ` [PATCH 1/3] btrfs-progs: print-tree: use ARRAY_SIZE() to replace open-coded ones Qu Wenruo
2024-10-04 5:52 ` [PATCH 2/3] btrfs-progs: print-tree: cleanup __print_readable_flag() Qu Wenruo
2024-10-04 5:52 ` [PATCH 3/3] btrfs-progs: print-tree: use readable_flag_entry for inode flags Qu Wenruo
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.1728020867.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.