From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/3] btrfs: extra debug output for sector size < page size cases
Date: Wed, 27 Nov 2024 14:36:35 +1030 [thread overview]
Message-ID: <cover.1732680197.git.wqu@suse.com> (raw)
The first patch is the long existing bug that full subpage bitmap dump
is not working for checked bitmap.
Thankfully even myself is not affected by the bug.
The second one is for a crash I hit where ASSERT() got triggered in
btrfs_folio_set_locked() after a btrfs_run_delalloc_range() failure.
The last one is for the btrfs_run_delalloc_range() failure, which is
not that rare in my environment, I guess the unsafe cache mode for my
aarch64 VM makes it too easy to hit ENOSPC.
But ENOSPC from btrfs_run_delalloc_range() itself is already a problem
for our data/metadata space reservation code, thus it should be
outputted even for non-debug build.
Qu Wenruo (3):
btrfs: subpage: fix the bitmap dump for the locked flags
btrfs: subpage: dump the involved bitmap when ASSERT() failed
btrfs: add extra error messages for extent_writepage() failure
fs/btrfs/extent_io.c | 16 +++++++++++++++
fs/btrfs/subpage.c | 47 ++++++++++++++++++++++++++++++++------------
2 files changed, 50 insertions(+), 13 deletions(-)
--
2.47.0
next reply other threads:[~2024-11-27 4:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 4:06 Qu Wenruo [this message]
2024-11-27 4:06 ` [PATCH 1/3] btrfs: subpage: fix the bitmap dump for the locked flags Qu Wenruo
2024-11-27 4:06 ` [PATCH 2/3] btrfs: subpage: dump the involved bitmap when ASSERT() failed Qu Wenruo
2024-11-27 15:32 ` David Sterba
2024-11-27 4:06 ` [PATCH 3/3] btrfs: add extra error messages for extent_writepage() failure Qu Wenruo
2024-11-27 15:30 ` [PATCH 0/3] btrfs: extra debug output for sector size < page size cases David Sterba
2024-11-27 20:30 ` Qu Wenruo
2024-11-28 13:10 ` David Sterba
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.1732680197.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.