From: syzbot <syzbot+592e2ab8775dbe0bf09a@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, penguin-kernel@i-love.sakura.ne.jp,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernel?] INFO: task hung in uevent_show (2)
Date: Sat, 12 Jul 2025 08:18:03 -0700 [thread overview]
Message-ID: <68727cab.a00a0220.26a83e.0082.GAE@google.com> (raw)
In-Reply-To: <2ac5d313-c754-4fb9-acd3-21f3b948d653@I-love.SAKURA.ne.jp>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
INFO: task hung in corrupted
INFO: task syz.2.18:6947 blocked for more than 140 seconds.
Not tainted 6.16.0-rc5-syzkaller-00224-g379f604cc3dc-dirty #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.2.18 state:D
Tested on:
commit: 379f604c Merge tag 'pci-v6.16-fixes-3' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10a310f0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f481202e4ff2d138
dashboard link: https://syzkaller.appspot.com/bug?extid=592e2ab8775dbe0bf09a
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
patch: https://syzkaller.appspot.com/x/patch.diff?x=166b6d82580000
next prev parent reply other threads:[~2025-07-12 15:18 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-09 14:37 [syzbot] [usb?] INFO: task hung in uevent_show (2) syzbot
2024-11-10 0:59 ` syzbot
2025-07-10 11:05 ` Hillf Danton
2025-07-10 11:59 ` [syzbot] [kernel?] " syzbot
2025-07-10 12:59 ` [syzbot] [usb?] " Hillf Danton
2025-07-10 13:25 ` [syzbot] [kernel?] " syzbot
2025-07-09 4:39 ` [syzbot] [usb?] " Tetsuo Handa
2025-07-09 14:03 ` [syzbot] [kernel?] " syzbot
2025-07-09 14:13 ` Tetsuo Handa
2025-07-09 14:27 ` Alan Stern
2025-07-09 14:44 ` Tetsuo Handa
2025-07-09 15:19 ` Alan Stern
2025-07-09 15:33 ` Tetsuo Handa
2025-07-09 15:41 ` Alan Stern
2025-07-10 10:17 ` Tetsuo Handa
2025-07-10 14:13 ` Alan Stern
2025-07-09 14:15 ` [syzbot] [usb?] " Tetsuo Handa
2025-07-09 14:44 ` [syzbot] [kernel?] " syzbot
2025-07-09 15:01 ` Tetsuo Handa
2025-07-11 11:09 ` [syzbot] [usb?] " Tetsuo Handa
2025-07-11 11:44 ` [syzbot] [kernel?] " syzbot
2025-07-11 11:52 ` [syzbot] [usb?] " Tetsuo Handa
2025-07-11 12:13 ` [syzbot] [kernel?] " syzbot
2025-07-11 13:34 ` [syzbot] [usb?] " Tetsuo Handa
2025-07-11 14:09 ` [syzbot] [kernel?] " syzbot
2025-07-11 15:01 ` [syzbot] [usb?] " Tetsuo Handa
2025-07-11 15:46 ` [syzbot] [kernel?] " syzbot
2025-07-12 14:40 ` [syzbot] [usb?] " Tetsuo Handa
2025-07-12 15:18 ` syzbot [this message]
2025-07-12 15:41 ` Tetsuo Handa
2025-07-12 17:43 ` [syzbot] [kernel?] " syzbot
2025-07-13 7:50 ` [PATCH] media: imon: make send_packet() more robust Tetsuo Handa
2025-07-13 8:11 ` Hillf Danton
2025-07-13 15:21 ` Alan Stern
2025-07-15 20:19 ` Sean Young
2025-07-16 1:30 ` Alan Stern
2025-07-16 9:38 ` Sean Young
2025-07-16 10:09 ` Tetsuo Handa
2025-07-16 11:55 ` Hillf Danton
2025-07-16 12:47 ` Sean Young
2025-07-16 14:07 ` [PATCH v2] " Tetsuo Handa
2025-07-16 14:45 ` Alan Stern
2025-07-17 14:21 ` [PATCH v3] " Tetsuo Handa
2025-07-16 14:38 ` [PATCH] " Alan Stern
2025-07-13 8:29 ` [syzbot] [kernel?] INFO: task hung in uevent_show (2) 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=68727cab.a00a0220.26a83e.0082.GAE@google.com \
--to=syzbot+592e2ab8775dbe0bf09a@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--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 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.