From: syzbot <syzbot+cba6270878c89ed64a2d@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, brauner@kernel.org, dave@stgolabs.net,
frank.li@vivo.com, glaubitz@physik.fu-berlin.de, jack@suse.cz,
jfs-discussion@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, mcgrof@kernel.org, shaggy@kernel.org,
slava@dubeyko.com, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk, willy@infradead.org
Subject: Re: [syzbot] [hfs?] INFO: task hung in deactivate_super (3)
Date: Mon, 01 Sep 2025 00:59:01 -0700 [thread overview]
Message-ID: <68b55245.050a0220.3db4df.01bc.GAE@google.com> (raw)
In-Reply-To: <00000000000091e466061cee5be7@google.com>
syzbot has bisected this issue to:
commit 5b67d43976828dea2394eae2556b369bb7a61f64
Author: Davidlohr Bueso <dave@stgolabs.net>
Date: Fri Apr 18 01:59:17 2025 +0000
fs/buffer: use sleeping version of __find_get_block()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=101ba1f0580000
start commit: c8bc81a52d5a Merge tag 'arm64-fixes' of git://git.kernel.o..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=121ba1f0580000
console output: https://syzkaller.appspot.com/x/log.txt?x=141ba1f0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=bd9738e00c1bbfb4
dashboard link: https://syzkaller.appspot.com/bug?extid=cba6270878c89ed64a2d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10857a62580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14f5ce34580000
Reported-by: syzbot+cba6270878c89ed64a2d@syzkaller.appspotmail.com
Fixes: 5b67d4397682 ("fs/buffer: use sleeping version of __find_get_block()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-09-01 7:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 1:05 [syzbot] [jfs?] INFO: task hung in deactivate_super (3) syzbot
2025-08-31 12:06 ` [syzbot] [hfs?] " syzbot
2025-09-01 7:59 ` syzbot [this message]
2025-09-02 14:46 ` Davidlohr Bueso
2025-09-06 13:30 ` Tetsuo Handa
2025-09-07 2:03 ` Hillf Danton
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=68b55245.050a0220.3db4df.01bc.GAE@google.com \
--to=syzbot+cba6270878c89ed64a2d@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=dave@stgolabs.net \
--cc=frank.li@vivo.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=jack@suse.cz \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mcgrof@kernel.org \
--cc=shaggy@kernel.org \
--cc=slava@dubeyko.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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.