From: Siddharth Mishra <smish149@asu.edu>
To: David Sterba <dsterba@suse.com>
Cc: Qu Wenruo <wqu@suse.com>, Boris Burkov <boris@bur.io>,
Chris Mason <mason@kernel.org>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Siddharth Mishra <smish149@asu.edu>
Subject: [PATCH 0/2] btrfs: tree-checker: reject simple quota metadata without SIMPLE_QUOTA
Date: Mon, 2 Nov 2026 20:49:30 -0700 [thread overview]
Message-ID: <20261103034932.1790235-1-smish149@asu.edu> (raw)
Simple quotas put two types of metadata on the disk : the status item
with SIMPLE_MODE, and the owner ref in an extent item. These two types
are correct only when the super block has the SIMPLE_QUOTA bit. Several
functions ASSERT() this rule. The tree-checker does not enforce it :
- The tree-checker does not examine the status item. A status item
with SIMPLE_MODE and no SIMPLE_QUOTA bit causes a BUG at mount, in
qgroup_read_enable_gen(). Patch 1 adds a check.
- For an owner ref without the SIMPLE_QUOTA bit, check_extent_item()
gives a WARN_ON() and accepts the leaf. When btrfs frees the extent,
btrfs_get_extent_inline_ref_type() causes a BUG. Patch 2 rejects the
leaf. syzbot found both symptoms in 2024, without a reproducer.
Two sources can put these states on a disk : a damaged or crafted
image, and a power failure just after simple quotas were enabled on a
kernel without commit f2363e6fcc79 ("btrfs: fix transaction atomicity
bug when enabling simple quotas").
I reproduced both problems with crafted images on for-next. With the
patches, the tree-checker rejects the bad leaf. With patch 1, btrfs
then mounts the filesystem without quotas. With patch 2, the mount
fails. A clean simple quota filesystem still mounts, writes data, frees
extents and mounts again.
Siddharth Mishra (2):
btrfs: tree-checker: validate qgroup status item
btrfs: tree-checker: reject extent owner ref without simple quota
fs/btrfs/tree-checker.c | 41 ++++++++++++++++++++++++++++++++++++++++-
1 file changed, 40 insertions(+), 1 deletion(-)
base-commit: d6f76ca0a70d0c814731394a625ff0dc1feb390e
--
2.54.0
next reply other threads:[~2026-11-03 3:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 3:49 Siddharth Mishra [this message]
2026-11-03 3:49 ` [PATCH 1/2] btrfs: tree-checker: validate qgroup status item Siddharth Mishra
2026-11-03 4:36 ` Qu Wenruo
2026-11-03 3:49 ` [PATCH 2/2] btrfs: tree-checker: reject extent owner ref without simple quota Siddharth Mishra
2026-11-03 4:40 ` Qu Wenruo
2026-11-03 5:15 ` Siddharth Mishra
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=20261103034932.1790235-1-smish149@asu.edu \
--to=smish149@asu.edu \
--cc=boris@bur.io \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@kernel.org \
--cc=wqu@suse.com \
/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
all inboxes | Powered by JetHome®