Linux PCI subsystem development
 help / color / mirror / Atom feed
From: "Krzysztof Wilczyński" <kwilczynski@kernel.org>
To: Lorenzo Pieralisi <lpieralisi@kernel.org>
Cc: "Bjorn Helgaas" <helgaas@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Manivannan Sadhasivam" <mani@kernel.org>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	"Lukas Wunner" <lukas@wunner.de>,
	"Shuan He" <heshuan@bytedance.com>,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI/proc: Fix race between pci_proc_init() and pci_bus_add_device()
Date: Wed, 6 May 2026 08:53:14 +0900	[thread overview]
Message-ID: <20260505234738.GC1410272@rocinante> (raw)
In-Reply-To: <afm8y+KHlgtSWBqH@lpieralisi>

Hello,

> > > Lorenzo Pieralisi did some testing reported outside the mailing list (we
> > > talked on IRC) on the platform he had some boot issues.  With this patch
> > > applied, the problems seen before were resolved.
> > 
> > Thanks!  Can we include a link to the problem report and maybe a
> > couple lines of the symptoms?
> 
> You can add a Link tag:
> 
> https://lore.kernel.org/linux-pci/20250702155112.40124-2-heshuan@bytedance.com/
> 
> FWIW I tested it on top of:
> 
> https://lore.kernel.org/lkml/20260505-gic-v5-acpi-iwb-probe-deferral-v1-0-b37b85998362@kernel.org/
> 
> so:
> 
> Tested-by: Lorenzo Pieralisi <lpieralisi@kernel.org>
> 
> > Also the analysis of Sashiko feedback?
> 
> I have not looked into this yet though I/We should.
> 
> Thanks for the fix !

Thank you for taking the time to test it!  Much appreciated.

	Krzysztof

      reply	other threads:[~2026-05-05 23:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-30  0:35 [PATCH] PCI/proc: Fix race between pci_proc_init() and pci_bus_add_device() Krzysztof Wilczyński
2026-05-01  1:22 ` Krzysztof Wilczyński
2026-05-01 19:37   ` Bjorn Helgaas
2026-05-05  9:47     ` Lorenzo Pieralisi
2026-05-05 23:53       ` Krzysztof Wilczyński [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=20260505234738.GC1410272@rocinante \
    --to=kwilczynski@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=helgaas@kernel.org \
    --cc=heshuan@bytedance.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=lukas@wunner.de \
    --cc=mani@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