From: syzbot <syzbot+1bfacdf603474cfa86bd@syzkaller.appspotmail.com>
To: Yuezhang.Mo@sony.com, adilger.kernel@dilger.ca, bp@alien8.de,
brauner@kernel.org, casey@schaufler-ca.com,
dave.hansen@linux.intel.com, hpa@zytor.com, jack@suse.cz,
linkinjeon@kernel.org, linux-ext4@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
mingo@redhat.com, roberto.sassu@huawei.com,
sj1557.seo@samsung.com, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, tytso@mit.edu, viro@zeniv.linux.org.uk,
x86@kernel.org, yuezhang.mo@sony.com
Subject: Re: [syzbot] [exfat?] INFO: task hung in lock_two_directories (4)
Date: Wed, 03 Sep 2025 05:50:04 -0700 [thread overview]
Message-ID: <68b8397c.050a0220.3db4df.01f1.GAE@google.com> (raw)
In-Reply-To: <682ff0bf.a70a0220.1765ec.0148.GAE@google.com>
syzbot suspects this issue was fixed by commit:
commit 99f9a97dce39ad413c39b92c90393bbd6778f3fd
Author: Yuezhang Mo <Yuezhang.Mo@sony.com>
Date: Tue Mar 18 09:00:49 2025 +0000
exfat: add cluster chain loop check for dir
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13445e62580000
start commit: 3f31a806a62e Merge tag 'mm-hotfixes-stable-2025-07-11-16-1..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=bd2783a0a99d4ed0
dashboard link: https://syzkaller.appspot.com/bug?extid=1bfacdf603474cfa86bd
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=134b50f0580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16d7018c580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: exfat: add cluster chain loop check for dir
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-09-03 12:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 3:51 [syzbot] [ext4?] INFO: task hung in lock_two_directories (4) syzbot
2025-09-03 12:50 ` syzbot [this message]
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=68b8397c.050a0220.3db4df.01f1.GAE@google.com \
--to=syzbot+1bfacdf603474cfa86bd@syzkaller.appspotmail.com \
--cc=Yuezhang.Mo@sony.com \
--cc=adilger.kernel@dilger.ca \
--cc=bp@alien8.de \
--cc=brauner@kernel.org \
--cc=casey@schaufler-ca.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jack@suse.cz \
--cc=linkinjeon@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=roberto.sassu@huawei.com \
--cc=sj1557.seo@samsung.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.