linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ethan Zhao <haifeng.zhao@linux.intel.com>
To: Hongchen Zhang <zhanghongchen@loongson.cn>,
	Markus Elfring <Markus.Elfring@web.de>,
	Bjorn Helgaas <bhelgaas@google.com>
Cc: Alex Belits <abelits@marvell.com>,
	"Peter Zijlstra (Intel)" <peterz@infradead.org>,
	Nitesh Narayan Lal <nitesh@redhat.com>,
	Frederic Weisbecker <frederic@kernel.org>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	loongarch@lists.linux.dev, stable@vger.kernel.org,
	Huacai Chen <chenhuacai@loongson.cn>
Subject: Re: [PATCH v3] PCI: pci_call_probe: call local_pci_probe() when selected cpu is offline
Date: Mon, 22 Jul 2024 15:39:39 +0800	[thread overview]
Message-ID: <a50b3865-8a04-4a9a-8d27-b317619a75c0@linux.intel.com> (raw)
In-Reply-To: <20240613074258.4124603-1-zhanghongchen@loongson.cn>


On 6/13/2024 3:42 PM, Hongchen Zhang wrote:
> Call work_on_cpu(cpu, fn, arg) in pci_call_probe() while the argument
> @cpu is a offline cpu would cause system stuck forever.
>
> This can be happen if a node is online while all its CPUs are
> offline (We can use "maxcpus=1" without "nr_cpus=1" to reproduce it).
>
> So, in the above case, let pci_call_probe() call local_pci_probe()
> instead of work_on_cpu() when the best selected cpu is offline.
>
> Fixes: 69a18b18699b ("PCI: Restrict probe functions to housekeeping CPUs")
> Cc: <stable@vger.kernel.org>
> Signed-off-by: Huacai Chen <chenhuacai@loongson.cn>
> Signed-off-by: Hongchen Zhang <zhanghongchen@loongson.cn>
> ---
> v2 -> v3: Modify commit message according to Markus's suggestion
> v1 -> v2: Add a method to reproduce the problem
> ---
>   drivers/pci/pci-driver.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/pci/pci-driver.c b/drivers/pci/pci-driver.c
> index af2996d0d17f..32a99828e6a3 100644
> --- a/drivers/pci/pci-driver.c
> +++ b/drivers/pci/pci-driver.c
> @@ -386,7 +386,7 @@ static int pci_call_probe(struct pci_driver *drv, struct pci_dev *dev,
>   		free_cpumask_var(wq_domain_mask);
>   	}
>   
> -	if (cpu < nr_cpu_ids)

Why not choose the right cpu to callwork_on_cpu() ? the one that is online. Thanks, Ethan

> +	if ((cpu < nr_cpu_ids) && cpu_online(cpu))
>   		error = work_on_cpu(cpu, local_pci_probe, &ddi);
>   	else
>   		error = local_pci_probe(&ddi);

  parent reply	other threads:[~2024-07-22  7:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-13  7:42 [PATCH v3] PCI: pci_call_probe: call local_pci_probe() when selected cpu is offline Hongchen Zhang
2024-07-22  2:11 ` Huacai Chen
2024-07-22  7:39 ` Ethan Zhao [this message]
2024-07-24  1:58   ` Hongchen Zhang
2024-07-24  2:47     ` Ethan Zhao
2024-07-24  3:09       ` Hongchen Zhang
2024-07-24  6:40         ` Ethan Zhao
2024-07-24  7:05           ` Hongchen Zhang
2024-09-13  8:06             ` Huacai Chen

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=a50b3865-8a04-4a9a-8d27-b317619a75c0@linux.intel.com \
    --to=haifeng.zhao@linux.intel.com \
    --cc=Markus.Elfring@web.de \
    --cc=abelits@marvell.com \
    --cc=bhelgaas@google.com \
    --cc=chenhuacai@loongson.cn \
    --cc=frederic@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=loongarch@lists.linux.dev \
    --cc=nitesh@redhat.com \
    --cc=peterz@infradead.org \
    --cc=stable@vger.kernel.org \
    --cc=zhanghongchen@loongson.cn \
    /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;
as well as URLs for NNTP newsgroup(s).