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: fix generic/795 crash for bs > ps cases
Date: Fri, 31 Jul 2026 10:14:48 +0930	[thread overview]
Message-ID: <cover.1785457950.git.wqu@suse.com> (raw)

During my development of the incoming data_size feature, it turns out
that we have a new crash triggered by the new test case, generic/795 on
bs > ps cases.

It turns out that for cached inode items (btrfs_delayed_node) we can
skip the inode mapping flag settings.

This bug is fixed by the first path.

The second patch is to introduce the extra debug ASSERT()s, which
greatly reduced the search range by showing the mapping's minimal folio
order.

Qu Wenruo (2):
  btrfs: initialize inode mapping flags for cached inodes
  btrfs: add extra ASSERT()s to make sure the folio size is correct

 fs/btrfs/extent_io.c | 19 +++++++++++++++++++
 fs/btrfs/inode.c     |  3 ++-
 2 files changed, 21 insertions(+), 1 deletion(-)

-- 
2.54.0


             reply	other threads:[~2026-07-31  0:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-31  0:44 Qu Wenruo [this message]
2026-07-31  0:44 ` [PATCH 1/2] btrfs: initialize inode mapping flags for cached inodes Qu Wenruo
2026-07-31  0:44 ` [PATCH 2/2] btrfs: add extra ASSERT()s to make sure the folio size is correct Qu Wenruo
2026-07-31  9:22 ` [PATCH 0/2] btrfs: fix generic/795 crash for bs > ps cases Filipe Manana

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.1785457950.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