From: Edward Adam Davis <eadavis@qq.com>
To: eadavis@qq.com
Cc: axboe@kernel.dk, konishi.ryusuke@gmail.com, kristian@klausen.dk,
linux-kernel@vger.kernel.org, linux-nilfs@vger.kernel.org,
slava@dubeyko.com, syzkaller-bugs@googlegroups.com
Subject: [PATCH v3] nilfs2: Fix potential block overflow that cause system hang
Date: Thu, 18 Dec 2025 12:22:15 +0800 [thread overview]
Message-ID: <tencent_62C5D2DF8647899D2EE26EECCC8CA7C44606@qq.com> (raw)
In-Reply-To: <tencent_84D71B07255DBA68BBE733F89E1F1B344B08@qq.com>
When a user executes the FITRIM command, an underflow can occur when
calculating nblocks if end_block is too small. Since nblocks is of
type sector_t, which is u64, a negative nblocks value will become a
very large positive integer. This ultimately leads to the block layer
function __blkdev_issue_discard() taking an excessively long time to
process the bio chain, and the ns_segctor_sem lock remains held for a
long period. This prevents other tasks from acquiring the ns_segctor_sem
lock, resulting in the hang reported by syzbot in [1].
If the ending block is too small, for example, smaller than first data
block, this poses a risk of corrupting the filesystem's superblock.
Here, I check if the segment's ending block number is 0 to determine
if the previously calculated ending block is too small.
Although the start and len values in the user input range are too small,
a conservative strategy is adopted here to safely ignore them, which is
equivalent to a no-op; it will not perform any trimming and will not
throw an error.
[1]
task:segctord state:D stack:28968 pid:6093 tgid:6093 ppid:2 task_flags:0x200040 flags:0x00080000
Call Trace:
rwbase_write_lock+0x3dd/0x750 kernel/locking/rwbase_rt.c:272
nilfs_transaction_lock+0x253/0x4c0 fs/nilfs2/segment.c:357
nilfs_segctor_thread_construct fs/nilfs2/segment.c:2569 [inline]
nilfs_segctor_thread+0x6ec/0xe00 fs/nilfs2/segment.c:2684
Fixes: 82e11e857be3 ("nilfs2: add nilfs_sufile_trim_fs to trim clean segs")
Reported-by: syzbot+7eedce5eb281acd832f0@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=7eedce5eb281acd832f0
Signed-off-by: Edward Adam Davis <eadavis@qq.com>
---
v2 -> v3: change to segment end check and update comments
v1 -> v2: continue do discard and comments
fs/nilfs2/sufile.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/fs/nilfs2/sufile.c b/fs/nilfs2/sufile.c
index 83f93337c01b..fa612d5ec726 100644
--- a/fs/nilfs2/sufile.c
+++ b/fs/nilfs2/sufile.c
@@ -1095,6 +1095,8 @@ int nilfs_sufile_trim_fs(struct inode *sufile, struct fstrim_range *range)
segnum = nilfs_get_segnum_of_block(nilfs, start_block);
segnum_end = nilfs_get_segnum_of_block(nilfs, end_block);
+ if (!segnum_end)
+ return 0;
down_read(&NILFS_MDT(sufile)->mi_sem);
--
2.43.0
next prev parent reply other threads:[~2025-12-18 4:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 0:46 [syzbot] [nilfs?] INFO: task hung in nilfs_segctor_thread (6) syzbot
2025-12-17 8:43 ` [PATCH] nilfs2: fix potential block overflow that cause system hang Edward Adam Davis
2025-12-17 13:38 ` Ryusuke Konishi
2025-12-18 2:28 ` [PATCH v2] nilfs2: Fix " Edward Adam Davis
2025-12-18 4:22 ` Edward Adam Davis [this message]
2025-12-18 11:32 ` [PATCH v3] " Ryusuke Konishi
2025-12-18 11:48 ` [PATCH v4] " Edward Adam Davis
2025-12-18 12:01 ` Ryusuke Konishi
2025-12-18 12:10 ` [PATCH v5] " Edward Adam Davis
2025-12-18 12:42 ` Ryusuke Konishi
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=tencent_62C5D2DF8647899D2EE26EECCC8CA7C44606@qq.com \
--to=eadavis@qq.com \
--cc=axboe@kernel.dk \
--cc=konishi.ryusuke@gmail.com \
--cc=kristian@klausen.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=slava@dubeyko.com \
--cc=syzkaller-bugs@googlegroups.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®