From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Anand Jain <anand.jain@oracle.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: add CHANGING_FSID_V2 to print-tree
Date: Wed, 31 May 2023 10:08:26 +0800 [thread overview]
Message-ID: <48115fe9-e181-9045-3d10-e1549e67478d@gmx.com> (raw)
In-Reply-To: <9ffdb317-e679-0fb9-4181-c40526d7668d@gmx.com>
On 2023/5/31 08:01, Qu Wenruo wrote:
>
>
> On 2023/5/30 18:15, Anand Jain wrote:
>> Add the DEF_SUPER_FLAG_ENTRY for CHANGING_FSID_V2 to our btrfs-progs'
>> print-tree.c, as it is currently missing in the dump-super output, which
>> was too confusing.
>>
>> Before:
>> flags 0x1000000001
>> ( WRITTEN )
But my concern is, why we didn't show something like " | Unknown flags
..." in the first place?
Isn't this a bug already?
Thanks,
Qu
>>
>> After:
>> flags 0x1000000001
>> ( WRITTEN |
>> CHANGING_FSID_V2 )
>>
>> Signed-off-by: Anand Jain <anand.jain@oracle.com>
>
> The patch itself looks fine.
>
> Reviewed-by: Qu Wenruo <wqu@suse.com>
>
> Thanks,
> Qu
>> ---
>> kernel-shared/print-tree.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/kernel-shared/print-tree.c b/kernel-shared/print-tree.c
>> index aaaf58ae2e0f..623f192aaefc 100644
>> --- a/kernel-shared/print-tree.c
>> +++ b/kernel-shared/print-tree.c
>> @@ -1721,6 +1721,7 @@ static struct readable_flag_entry
>> super_flags_array[] = {
>> DEF_HEADER_FLAG_ENTRY(WRITTEN),
>> DEF_HEADER_FLAG_ENTRY(RELOC),
>> DEF_SUPER_FLAG_ENTRY(CHANGING_FSID),
>> + DEF_SUPER_FLAG_ENTRY(CHANGING_FSID_V2),
>> DEF_SUPER_FLAG_ENTRY(SEEDING),
>> DEF_SUPER_FLAG_ENTRY(METADUMP),
>> DEF_SUPER_FLAG_ENTRY(METADUMP_V2)
next prev parent reply other threads:[~2023-05-31 2:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 10:15 [PATCH] btrfs-progs: add CHANGING_FSID_V2 to print-tree Anand Jain
2023-05-30 12:37 ` David Sterba
2023-05-31 5:46 ` Anand Jain
2023-05-31 11:00 ` David Sterba
2023-05-31 0:01 ` Qu Wenruo
2023-05-31 2:08 ` Qu Wenruo [this message]
2023-05-31 7:56 ` Anand Jain
2023-05-31 8:06 ` [PATCH v2] " Anand Jain
2023-05-31 8:15 ` Qu Wenruo
2023-05-31 23:42 ` 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=48115fe9-e181-9045-3d10-e1549e67478d@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=anand.jain@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox