From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+c5c9c223a721d7353490@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ext4?] possible deadlock in ext4_truncate (2)
Date: Mon, 25 Aug 2025 18:41:52 +0800 [thread overview]
Message-ID: <20250825104155.5420-1-hdanton@sina.com> (raw)
In-Reply-To: <68ac2412.050a0220.37038e.0089.GAE@google.com>
> Date: Mon, 25 Aug 2025 01:51:30 -0700 [thread overview]
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 8d245acc1e88 Merge tag 'char-misc-6.17-rc3' of git://git.k..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1654ac42580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=da02162f945f3311
> dashboard link: https://syzkaller.appspot.com/bug?extid=c5c9c223a721d7353490
> compiler: gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15d1cef0580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10f4e7bc580000
#syz test
--- x/fs/ext4/inode.c
+++ y/fs/ext4/inode.c
@@ -4573,6 +4573,7 @@ int ext4_truncate(struct inode *inode)
struct ext4_inode_info *ei = EXT4_I(inode);
unsigned int credits;
int err = 0, err2;
+ static int subclass = 0;
handle_t *handle;
struct address_space *mapping = inode->i_mapping;
@@ -4636,7 +4637,7 @@ int ext4_truncate(struct inode *inode)
ext4_fc_track_inode(handle, inode);
ext4_check_map_extents_env(inode);
- down_write(&EXT4_I(inode)->i_data_sem);
+ down_write_nested(&EXT4_I(inode)->i_data_sem, subclass++);
ext4_discard_preallocations(inode);
if (ext4_test_inode_flag(inode, EXT4_INODE_EXTENTS))
--
next prev parent reply other threads:[~2025-08-25 10:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 8:51 syzbot
2025-08-25 10:41 ` Hillf Danton [this message]
2025-08-25 13:11 ` syzbot
2025-08-25 13:37 ` Theodore Ts'o
2025-08-26 3:46 ` Hillf Danton
2025-08-26 1:43 ` Hillf Danton
2025-08-26 2:32 ` syzbot
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=20250825104155.5420-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+c5c9c223a721d7353490@syzkaller.appspotmail.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®