All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Danilo Krummrich" <dakr@kernel.org>
To: "Geert Uytterhoeven" <geert@linux-m68k.org>
Cc: "Biju" <biju.das.au@gmail.com>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	"Biju Das" <biju.das.jz@bp.renesas.com>,
	<driver-core@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
	"Geert Uytterhoeven" <geert+renesas@glider.be>,
	"Prabhakar Mahadev Lad" <prabhakar.mahadev-lad.rj@bp.renesas.com>,
	<linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH] Revert "driver core: Use mod_delayed_work to prevent lost deferred probe work"
Date: Tue, 26 May 2026 14:48:40 +0200	[thread overview]
Message-ID: <DISMCG7D9WRT.3BLQZMEGSWXDB@kernel.org> (raw)
In-Reply-To: <CAMuHMdUzjj3dE3wQ84XGoP7RAfKxRAChPnbzkAW8NnrPhtoeoA@mail.gmail.com>

On Tue May 26, 2026 at 2:46 PM CEST, Geert Uytterhoeven wrote:
> Hi Danilo,
>
> On Tue, 26 May 2026 at 14:09, Danilo Krummrich <dakr@kernel.org> wrote:
>> On 5/26/26 2:03 PM, Biju wrote:
>> > From: Biju Das <biju.das.jz@bp.renesas.com>
>> >
>> > Commit 1137838865bf ("driver core: Use mod_delayed_work to prevent lost
>> > deferred probe work") introduced below regression on Renesas SMARC RZ/G2L
>> > EVK:
>> >  class_for_each_device called for class 'devlink' before it was registered
>> >  WARNING: drivers/base/class.c:415 at class_for_each_device+0x12c/0x13c, CPU#1: kworker/1:1/26
>> >  class_for_each_device+0x12c/0x13c (P)
>> >  fw_devlink_probing_done+0x58/0xa0
>> >  deferred_probe_timeout_work_func+0x5c/0xb8
>> >  process_one_work+0x150/0x290
>> >  worker_thread+0x18c/0x300
>> >  kthread+0x114/0x120
>> >
>> > Reverting the commit fixes the issue.
>> There's already [1], which should also fix the issue.
>
> Thanks!
>
> FTR, that patch is not sufficient to fix the WARNING (on RZ/Five)
> for me: I need both patches from the series to get rid of the both
> the warning thousands of "sync_state() pending due to" and
> hundreds of "deferred probe pending" messages on other Renesas systems.

Yes, with linking to [1] I meant both patches.

Thanks,
Danilo

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

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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-26 12:03 [PATCH] Revert "driver core: Use mod_delayed_work to prevent lost deferred probe work" Biju
2026-05-26 12:09 ` Danilo Krummrich
2026-05-26 12:14   ` Biju Das
2026-05-26 12:15     ` Danilo Krummrich
2026-05-26 12:46   ` Geert Uytterhoeven
2026-05-26 12:48     ` 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=DISMCG7D9WRT.3BLQZMEGSWXDB@kernel.org \
    --to=dakr@kernel.org \
    --cc=biju.das.au@gmail.com \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=driver-core@lists.linux.dev \
    --cc=geert+renesas@glider.be \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --cc=rafael@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.