From: Bjorn Helgaas <helgaas@kernel.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
Konrad Dybcio <konradybcio@kernel.org>
Subject: Re: [PATCH v2] PCI: take the rescan lock when adding devices during host probe
Date: Sat, 12 Oct 2024 09:31:19 -0500 [thread overview]
Message-ID: <20241012143119.GA604156@bhelgaas> (raw)
In-Reply-To: <CAMRc=MeUW3jsOPTxxu38+w_ps2FQFYR-PmgGY=V+vjnqNs0RYw@mail.gmail.com>
On Thu, Oct 10, 2024 at 11:17:47AM +0200, Bartosz Golaszewski wrote:
> On Thu, Oct 3, 2024 at 10:43 AM Bartosz Golaszewski <brgl@bgdev.pl> wrote:
> >
> > From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> >
> > Since adding the PCI power control code, we may end up with a race
> > between the pwrctl platform device rescanning the bus and the host
> > controller probe function. The latter needs to take the rescan lock when
> > adding devices or we may end up in an undefined state having two
> > incompletely added devices and hit the following crash when trying to
> > remove the device over sysfs:
> >
> > Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
> > Internal error: Oops: 0000000096000004 [#1] SMP
> > Call trace:
> > __pi_strlen+0x14/0x150
> > kernfs_find_ns+0x80/0x13c
> > kernfs_remove_by_name_ns+0x54/0xf0
> > sysfs_remove_bin_file+0x24/0x34
> > pci_remove_resource_files+0x3c/0x84
> > pci_remove_sysfs_dev_files+0x28/0x38
> > pci_stop_bus_device+0x8c/0xd8
> > pci_stop_bus_device+0x40/0xd8
> > pci_stop_and_remove_bus_device_locked+0x28/0x48
> > remove_store+0x70/0xb0
> > dev_attr_store+0x20/0x38
> > sysfs_kf_write+0x58/0x78
> > kernfs_fop_write_iter+0xe8/0x184
> > vfs_write+0x2dc/0x308
> > ksys_write+0x7c/0xec
> >
> > Reported-by: Konrad Dybcio <konradybcio@kernel.org>
> > Tested-by: Konrad Dybcio <konradybcio@kernel.org>
> > Fixes: 4565d2652a37 ("PCI/pwrctl: Add PCI power control core code")
> > Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> > ---
>
> It's been a week, so gentle ping - can this be picked up into v6.12?
I hoped we could fix the similar latent issues in other drivers, but
yes, we can get this in v6.12. Thanks for the hint that it should go
there. I'll pick it up when I return from vacation on Wednesday.
Bjorn
next prev parent reply other threads:[~2024-10-12 14:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 8:43 Bartosz Golaszewski
2024-10-03 8:50 ` Manivannan Sadhasivam
2024-10-10 9:17 ` Bartosz Golaszewski
2024-10-12 14:31 ` Bjorn Helgaas [this message]
2024-10-14 12:21 ` Bartosz Golaszewski
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=20241012143119.GA604156@bhelgaas \
--to=helgaas@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=bhelgaas@google.com \
--cc=brgl@bgdev.pl \
--cc=konradybcio@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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®