From: syzbot <syzbot+f0b58a1f5075a90dd9a5@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, jack@suse.cz,
libaokun@linux.alibaba.com, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, ojaswin@linux.ibm.com,
ritesh.list@gmail.com, syzkaller-bugs@googlegroups.com,
tytso@mit.edu, yi.zhang@huawei.com, yun.zhou@windriver.com
Subject: Re: [syzbot] [ext4?] possible deadlock in ext4_xattr_set_handle (7)
Date: Thu, 22 Oct 2026 21:20:03 -0700 [thread overview]
Message-ID: <6adae073.d1cee5ca.8df35.0001.GAE@google.com> (raw)
In-Reply-To: <691591fd.a70a0220.3124cb.0020.GAE@google.com>
syzbot suspects this issue was fixed by commit:
commit 7461c60b9c6a839b13ad4c3490681a0cf5aa0637
Author: Yun Zhou <yun.zhou@windriver.com>
Date: Tue Jun 23 06:19:02 2026 +0000
ext4: skip extra isize expansion during mount to prevent deadlock
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=124e0a95580000
start commit: 61c03dfde854 Merge tag 'ntfs-for-7.2-rc3' of git://git.ker..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=98da55a882774dfe
dashboard link: https://syzkaller.appspot.com/bug?extid=f0b58a1f5075a90dd9a5
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=165aeb89580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10185432580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: ext4: skip extra isize expansion during mount to prevent deadlock
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2026-10-23 4:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 8:08 syzbot
2025-12-21 18:39 ` syzbot
2026-06-09 8:41 ` Forwarded: test syzbot
2026-10-23 4:20 ` syzbot [this message]
[not found] <36795559-b70e-4c03-b547-a355ca7f20e9@windriver.com>
2026-06-09 9:48 ` [syzbot] [ext4?] possible deadlock in ext4_xattr_set_handle (7) 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=6adae073.d1cee5ca.8df35.0001.GAE@google.com \
--to=syzbot+f0b58a1f5075a90dd9a5@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.cz \
--cc=libaokun@linux.alibaba.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojaswin@linux.ibm.com \
--cc=ritesh.list@gmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
--cc=yi.zhang@huawei.com \
--cc=yun.zhou@windriver.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®