linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Lukas Wunner <lukas@wunner.de>
Cc: Keith Busch <kbusch@kernel.org>,
	Ilpo Jarvinen <ilpo.jarvinen@linux.intel.com>,
	Joel Mathew Thomas <proxy0@tutamail.com>,
	tcm4095@gmail.com, linux-pci@vger.kernel.org
Subject: Re: [PATCH for-linus] PCI: pciehp: Ignore belated Presence Detect Changed caused by DPC
Date: Wed, 18 Jun 2025 10:13:07 -0500	[thread overview]
Message-ID: <20250618151307.GA1203119@bhelgaas> (raw)
In-Reply-To: <d9c4286a16253af7e93eaf12e076e3ef3546367a.1750257164.git.lukas@wunner.de>

On Wed, Jun 18, 2025 at 04:38:25PM +0200, Lukas Wunner wrote:
> Commit c3be50f7547c ("PCI: pciehp: Ignore Presence Detect Changed caused
> by DPC") sought to ignore Presence Detect Changed events occurring as a
> side effect of Downstream Port Containment.
> 
> The commit awaits recovery from DPC and then clears events which occurred
> in the meantime.  However if the first event seen after DPC is Data Link
> Layer State Changed, only that event is cleared and not Presence Detect
> Changed.  The object of the commit is thus defeated.
> 
> That's because pciehp_ist() computes the events to clear based on the
> local "events" variable instead of "ctrl->pending_events".  The former
> contains the events that had occurred when pciehp_ist() was entered,
> whereas the latter also contains events that have accumulated while
> awaiting DPC recovery.
> 
> In practice, the order of PDC and DLLSC events is arbitrary and the delay
> in-between can be several milliseconds.
> 
> So change the logic to always clear PDC events, even if they come after an
> initial DLLSC event.
> 
> Fixes: c3be50f7547c ("PCI: pciehp: Ignore Presence Detect Changed caused by DPC")
> Reported-by: Lương Việt Hoàng <tcm4095@gmail.com>
> Reported-by: Joel Mathew Thomas <proxy0@tutamail.com>
> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=219765#c165
> Tested-by: Lương Việt Hoàng <tcm4095@gmail.com>
> Tested-by: Joel Mathew Thomas <proxy0@tutamail.com>
> Signed-off-by: Lukas Wunner <lukas@wunner.de>

Applied to pci/for-linus for v6.16, thanks, Lukas!

> ---
>  drivers/pci/hotplug/pciehp_hpc.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/pci/hotplug/pciehp_hpc.c b/drivers/pci/hotplug/pciehp_hpc.c
> index ebd342b..91d2d92 100644
> --- a/drivers/pci/hotplug/pciehp_hpc.c
> +++ b/drivers/pci/hotplug/pciehp_hpc.c
> @@ -771,7 +771,7 @@ static irqreturn_t pciehp_ist(int irq, void *dev_id)
>  		u16 ignored_events = PCI_EXP_SLTSTA_DLLSC;
>  
>  		if (!ctrl->inband_presence_disabled)
> -			ignored_events |= events & PCI_EXP_SLTSTA_PDC;
> +			ignored_events |= PCI_EXP_SLTSTA_PDC;
>  
>  		events &= ~ignored_events;
>  		pciehp_ignore_link_change(ctrl, pdev, irq, ignored_events);
> -- 
> 2.47.2
> 

      reply	other threads:[~2025-06-18 15:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-18 14:38 [PATCH for-linus] PCI: pciehp: Ignore belated Presence Detect Changed caused by DPC Lukas Wunner
2025-06-18 15:13 ` Bjorn Helgaas [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=20250618151307.GA1203119@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=kbusch@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=proxy0@tutamail.com \
    --cc=tcm4095@gmail.com \
    /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).