From: kmpfqgdwxucqz9@gmail.com
To: David Sterba <dsterba@suse.com>
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
KernelKraze <admin@mail.free-proletariat.dpdns.org>
Subject: [PATCH 0/1] btrfs: strengthen integer overflow protection in batch allocation
Date: Wed, 30 Jul 2025 13:43:47 +0900 [thread overview]
Message-ID: <20250730044348.133387-1-admin@mail.free-proletariat.dpdns.org> (raw)
From: KernelKraze <admin@mail.free-proletariat.dpdns.org>
Hi,
This patch improves robustness in the btrfs filesystem by adding integer
overflow protection during batch allocation in flush_dir_items_batch().
The improvement was identified during a systematic code review of kernel
subsystems. Without proper bounds checking, theoretical integer overflow
could occur with extremely large directory item counts.
The fix implements proper overflow checking using the kernel's overflow
detection helpers and adds a reasonable upper limit consistent with other
btrfs batch operations.
This has been compile-tested and the fix aligns with existing patterns
in the btrfs codebase (log_delayed_insertion_items uses the same 195 limit).
The patch passes checkpatch.pl with no errors or warnings.
I've CC'd the btrfs maintainers for review.
Thanks,
KernelKraze
KernelKraze (1):
btrfs: add integer overflow protection to flush_dir_items_batch allocation
fs/btrfs/tree-log.c | 27 ++++++++++++++++++++++++---
1 file changed, 24 insertions(+), 3 deletions(-)
--
2.48.1
next reply other threads:[~2025-07-30 4:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 4:43 kmpfqgdwxucqz9 [this message]
2025-07-30 4:43 ` [PATCH 1/1] btrfs: add integer overflow protection to flush_dir_items_batch allocation kmpfqgdwxucqz9
2025-07-30 6:35 ` Johannes Thumshirn
2025-07-30 6:58 ` kmpfqgdwxucqz9
2025-07-30 7:06 ` Qu Wenruo
2025-07-30 7:20 ` [PATCH 1/1] btrfs: add integer overflow protection to flush_dir_items_batch allocation - WITHDRAWN kmpfqgdwxucqz9
2025-07-30 10:20 ` [PATCH 1/1] btrfs: add integer overflow protection to flush_dir_items_batch allocation 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=20250730044348.133387-1-admin@mail.free-proletariat.dpdns.org \
--to=kmpfqgdwxucqz9@gmail.com \
--cc=admin@mail.free-proletariat.dpdns.org \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).