From: CJ <firefly0158@163.com>
To: aivazian.tigran@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: INFO: task hung in bfs_lookup on v7.3-rc2
Date: Fri, 13 Nov 2026 11:37:39 +0800 (CST) [thread overview]
Message-ID: <2ba22cd7.31ed.1a1d2fb7d4d.Coremail.firefly0158@163.com> (raw)
Hi,
I am reporting a hung task in bfs_lookup. It is still reproducible on
Linux v7.3-rc2 (HEAD df2908090cda368b01ff43709f51890076c56157) with a syzkaller reproducer.
syzbot originally reported "INFO: task hung in bfs_lookup" on linux-6.1
(https://syzkaller.appspot.com/bug?extid=329c4002dad0055b432b). The target console shows a matching failure signature.
The reproducer mounts a crafted BFS image and performs a directory lookup while another path holds the directory lock.
On the target, the kernel reports:
INFO: task syz.0.11:9034 blocked for more than 143 seconds.
The diagnostic path is bfs_lookup -> d_alloc_parallel -> __d_lookup -> lookup_open.
The same blocked or diagnostic function path is present (bfs_lookup).
One possible cause is lock ordering between concurrent BFS directory operations.
This is a follow-up for an existing syzbot report and describes an
observed failure, not a bisected root cause.
Reproducer:
syz reproducer: https://pastebin.com/raw/b6XKQqyN
console output: https://pastebin.com/raw/DE2p85x3
kernel config: https://syzkaller.appspot.com/text?tag=KernelConfig&x=ff93ecc085d8436e
Kernel:
HEAD commit: df2908090cda368b01ff43709f51890076c56157
git tree: linux-stable
kernel version: 7.3.0-rc2
tested tag: v7.3-rc2
Let me know if you need more details or testing.
Thanks.
reply other threads:[~2026-11-13 3:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2ba22cd7.31ed.1a1d2fb7d4d.Coremail.firefly0158@163.com \
--to=firefly0158@163.com \
--cc=aivazian.tigran@gmail.com \
--cc=linux-kernel@vger.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 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®