Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/4] btrfs-progs: check: fix and refactor load_quota_info()
Date: Mon,  5 Oct 2026 19:31:09 +1030	[thread overview]
Message-ID: <cover.1791190852.git.wqu@suse.com> (raw)

The btrfs-check code of qgroup verification is pretty old, and there is
a long existing bug from day 1 that causes incorrect initial search
condition.

The first patch is to fix that bug.

Then the second one to reduce the memory usage of qgroup_count
structure.

The third one is to refactor load_quota_info() to follow the modern
standard and practice.

Finally add a test case as a regression test.

Qu Wenruo (4):
  btrfs-progs: check: fix the inverted condition to load qgroups
  btrfs-progs: check: remove unused qgroup_count::key
  btrfs-progs: check: refactor load_quota_info()
  btrfs-progs: fsck-tests: add a new test case for qgroup tree check

 check/qgroup-verify.c                         | 155 +++++++++---------
 tests/fsck-tests/076-large-quota-tree/test.sh |  28 ++++
 2 files changed, 103 insertions(+), 80 deletions(-)
 create mode 100644 tests/fsck-tests/076-large-quota-tree/test.sh

--
2.55.0


             reply	other threads:[~2026-10-05  9:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-05  9:01 Qu Wenruo [this message]
2026-10-05  9:01 ` [PATCH 1/4] btrfs-progs: check: fix the inverted condition to load qgroups Qu Wenruo
2026-10-05  9:01 ` [PATCH 2/4] btrfs-progs: check: remove unused qgroup_count::key Qu Wenruo
2026-10-05  9:01 ` [PATCH 3/4] btrfs-progs: check: refactor load_quota_info() Qu Wenruo
2026-10-05  9:01 ` [PATCH 4/4] btrfs-progs: fsck-tests: add a new test case for qgroup tree check 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.1791190852.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