public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/3] btrfs-progs: check/lowmem: fix false alerts on
Date: Sun, 12 Apr 2026 14:38:42 +0930	[thread overview]
Message-ID: <cover.1775970499.git.wqu@suse.com> (raw)

The lowmem mode check doesn't recognize the new EXTENT_OWNER_REF key
type, thus it will always treat it as an unknown inline type and cause
false alerts.

Fix it by adding such types to lowmem check.

The first patch is to fix a format string error during the add of inline
backref sequence output, which breaks the indent.

The second patch is the real fix for lowmem btrfs check on squota
feature.

The last one is a new test case for fsck on squota.

Qu Wenruo (3):
  btrfs-progs: print-tree: fix the format string for
    EXTENT_OWNER_REF_KEY
  btrfs-progs: check/lowmem: fix false alerts about EXTENT_OWNER
  btrfs-progs: fsck-tests: add a new test case for squota lowmem false
    alerts

 check/mode-lowmem.c                 |  7 +++++++
 kernel-shared/print-tree.c          |  2 +-
 tests/fsck-tests/073-squota/test.sh | 31 +++++++++++++++++++++++++++++
 3 files changed, 39 insertions(+), 1 deletion(-)
 create mode 100755 tests/fsck-tests/073-squota/test.sh

--
2.53.0


             reply	other threads:[~2026-04-12  5:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-12  5:08 Qu Wenruo [this message]
2026-04-12  5:08 ` [PATCH 1/3] btrfs-progs: print-tree: fix the format string for EXTENT_OWNER_REF_KEY Qu Wenruo
2026-04-12  5:08 ` [PATCH 2/3] btrfs-progs: check/lowmem: fix false alerts about EXTENT_OWNER Qu Wenruo
2026-04-12  5:08 ` [PATCH 3/3] btrfs-progs: fsck-tests: add a new test case for squota lowmem false alerts 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.1775970499.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