Linux driver-core infrastructure
 help / color / mirror / Atom feed
From: "Danilo Krummrich" <dakr@kernel.org>
To: "Tetsuo Handa" <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: "Zhang Yuwei" <zhangyuwei20@huawei.com>,
	<gregkh@linuxfoundation.org>,
	"syzbot" <syzbot+50b5f81fff158669504a@syzkaller.appspotmail.com>,
	<driver-core@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
	<linux-next@vger.kernel.org>, <rafael@kernel.org>,
	<sfr@canb.auug.org.au>, <syzkaller-bugs@googlegroups.com>
Subject: Re: [syzbot] [kernel?] linux-next test error: WARNING in class_for_each_device
Date: Tue, 26 May 2026 14:02:51 +0200	[thread overview]
Message-ID: <DISLDDGB663S.248HHW19FMX3M@kernel.org> (raw)
In-Reply-To: <a3ca7056-b215-4632-b86a-c722d82c35e6@I-love.SAKURA.ne.jp>

On Tue May 26, 2026 at 9:19 AM CEST, Tetsuo Handa wrote:
> On 2026/05/26 15:08, Tetsuo Handa wrote:
>> On 2026/05/26 14:55, syzbot wrote:
>>> Hello,
>>>
>>> syzbot found the following issue on:
>>>
>>> HEAD commit:    d387b06f7c15 Add linux-next specific files for 20260525
>>> git tree:       linux-next
>>> console output: https://syzkaller.appspot.com/x/log.txt?x=15eb7796580000
>>> kernel config:  https://syzkaller.appspot.com/x/.config?x=8dd72cf810e753a6
>>> dashboard link: https://syzkaller.appspot.com/bug?extid=50b5f81fff158669504a
>>> compiler:       Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
>>>
>>> Downloadable assets:
>>> disk image: https://storage.googleapis.com/syzbot-assets/39490dfbc250/disk-d387b06f.raw.xz
>>> vmlinux: https://storage.googleapis.com/syzbot-assets/0789ac7ac5fc/vmlinux-d387b06f.xz
>>> kernel image: https://storage.googleapis.com/syzbot-assets/4464df9f5ccf/bzImage-d387b06f.xz
>>>
>>> IMPORTANT: if you fix the issue, please add the following tag to the commit:
>>> Reported-by: syzbot+50b5f81fff158669504a@syzkaller.appspotmail.com
>>>
>>> ------------[ cut here ]------------
>>> class_for_each_device called for class 'devlink' before it was registered
>> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/base?id=1137838865bfc9a7cd5869c1dc5c22aa45ec12c8
>> 
>> Why "driver_deferred_probe_timeout * HZ" => "driver_deferred_probe_timeout" ?
>> 
>
> Here is an analysis from Google AI mode regarding this problem: https://share.google/aimode/UO1WnoKPDSbyjY5Qj
>
> Greg, can you immediately drop commit 1137838865bf ("driver core: Use mod_delayed_work to prevent
> lost deferred probe work") so that syzbot can resume testing linux-next tree as soon as possible?

I already posted patches to fix this in [1]. I will pick them up today.

[1] https://lore.kernel.org/driver-core/20260525012340.3860581-1-dakr@kernel.org/t/#u

      parent reply	other threads:[~2026-05-26 12:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-26  5:55 [syzbot] [kernel?] linux-next test error: WARNING in class_for_each_device syzbot
2026-05-26  6:08 ` Tetsuo Handa
2026-05-26  7:19   ` Tetsuo Handa
2026-05-26 11:59     ` Tetsuo Handa
2026-05-26 12:03       ` Danilo Krummrich
2026-05-26 12:02     ` Danilo Krummrich [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=DISLDDGB663S.248HHW19FMX3M@kernel.org \
    --to=dakr@kernel.org \
    --cc=driver-core@lists.linux.dev \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --cc=rafael@kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=syzbot+50b5f81fff158669504a@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=zhangyuwei20@huawei.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