Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs-progs: fix the conflicting super flags
Date: Sat,  8 Jun 2024 13:43:23 +0930	[thread overview]
Message-ID: <cover.1717819918.git.wqu@suse.com> (raw)

There is a github issue that a canceled csum conversion leaves a
CHANGING_FSID_V2 flag, which turns out to be conflicting super flags
(CHANGING_FSID_V2 and CHANGING_DATA_CSUM).

Fix the problem and output all supported flags for print-tree.

Qu Wenruo (2):
  btrfs-progs: fix the conflicting super flags
  btrfs-progs: print-tree: handle all supported flags

 kernel-shared/ctree.h           | 10 ----------
 kernel-shared/print-tree.c      | 35 ++++++++++++++++++---------------
 kernel-shared/uapi/btrfs_tree.h |  8 ++++++++
 3 files changed, 27 insertions(+), 26 deletions(-)

--
2.45.2


             reply	other threads:[~2024-06-08  4:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-08  4:13 Qu Wenruo [this message]
2024-06-08  4:13 ` [PATCH 1/2] btrfs-progs: fix the conflicting super flags Qu Wenruo
2024-06-08  4:13 ` [PATCH 2/2] btrfs-progs: print-tree: handle all supported flags Qu Wenruo
2024-06-08  5:07   ` 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.1717819918.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox