From: patchwork-bot+netdevbpf@kernel.org
To: Leon Romanovsky <leon@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, leonro@nvidia.com,
amcohen@nvidia.com, jiri@nvidia.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] devlink: Remove extra device_lock assert checks
Date: Tue, 19 Oct 2021 12:20:10 +0000 [thread overview]
Message-ID: <163464601092.7615.1219827050996715515.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <8bbcc624cf574a1f491a674e436dbd0673cb0127.1634629765.git.leonro@nvidia.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Tue, 19 Oct 2021 10:49:54 +0300 you wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> PCI core code in the pci_call_probe() has a path that doesn't hold
> device_lock. It happens because the ->probe() is called through the
> workqueue mechanism.
>
> 349 static int pci_call_probe(struct pci_driver *drv, struct pci_dev *dev,
> 350 const struct pci_device_id *id)
> 351 {
> 352
> ....
> 377 if (cpu < nr_cpu_ids)
> 378 error = work_on_cpu(cpu, local_pci_probe, &ddi);
>
> [...]
Here is the summary with links:
- [net-next] devlink: Remove extra device_lock assert checks
https://git.kernel.org/netdev/net-next/c/cb3dc8901ba4
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-10-19 12:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 7:49 [PATCH net-next] devlink: Remove extra device_lock assert checks Leon Romanovsky
2021-10-19 12:20 ` patchwork-bot+netdevbpf [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=163464601092.7615.1219827050996715515.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=amcohen@nvidia.com \
--cc=davem@davemloft.net \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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