From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>
Subject: [PATCH 0/6] Debugging macro and kmalloc_obj* cleanups
Date: Tue, 14 Apr 2026 17:30:28 +0200 [thread overview]
Message-ID: <cover.1776180388.git.dsterba@suse.com> (raw)
Replace some macros with existing or new API. Replacing ASSERT(0) in
free space tree updates error handling but it's for "impossible"
conditions.
David Sterba (6):
btrfs: move condition to WARN_ON in btrfs_set_delalloc_extent()
btrfs: replace open coded DEBUG_WARN in extent_writepage()
btrfs: handle unexpected free-space-tree key types
btrfs: lift assertions to beginning of insert_delayed_ref()
btrfs: do more kmalloc_obj()/kmalloc_objs() conversions
btrfs: convert kmalloc_array to kmalloc_objs in
btrfs_calc_avail_data_space()
fs/btrfs/delayed-ref.c | 5 ++++-
fs/btrfs/extent_io.c | 2 +-
fs/btrfs/free-space-tree.c | 18 +++++++++++++++---
fs/btrfs/inode.c | 3 +--
fs/btrfs/relocation.c | 10 +++++-----
fs/btrfs/super.c | 3 +--
6 files changed, 27 insertions(+), 14 deletions(-)
--
2.53.0
next reply other threads:[~2026-04-14 15:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 15:30 David Sterba [this message]
2026-04-14 15:30 ` [PATCH 1/6] btrfs: move condition to WARN_ON in btrfs_set_delalloc_extent() David Sterba
2026-04-14 15:30 ` [PATCH 2/6] btrfs: replace open coded DEBUG_WARN in extent_writepage() David Sterba
2026-04-14 15:30 ` [PATCH 3/6] btrfs: handle unexpected free-space-tree key types David Sterba
2026-04-14 15:30 ` [PATCH 4/6] btrfs: lift assertions to beginning of insert_delayed_ref() David Sterba
2026-04-14 15:30 ` [PATCH 5/6] btrfs: do more kmalloc_obj()/kmalloc_objs() conversions David Sterba
2026-04-14 15:30 ` [PATCH 6/6] btrfs: convert kmalloc_array to kmalloc_objs in btrfs_calc_avail_data_space() David Sterba
2026-04-14 15:52 ` [PATCH 0/6] Debugging macro and kmalloc_obj* cleanups Johannes Thumshirn
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.1776180388.git.dsterba@suse.com \
--to=dsterba@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