Linux PCI subsystem development
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Lukas Wunner <lukas@wunner.de>
Cc: sashiko-reviews@lists.linux.dev, linux-pci@vger.kernel.org
Subject: Re: [PATCH v2 2/2] PCI/AER: Check validity of Error Source ID register
Date: Fri, 6 Nov 2026 19:37:13 +0200 (EET)	[thread overview]
Message-ID: <36c2c56c-59c4-4183-70ec-5d05e88569b5@linux.intel.com> (raw)
In-Reply-To: <au4NiO-rglobvYxo@wunner.de>

[-- Attachment #1: Type: text/plain, Size: 1445 bytes --]

On Fri, 6 Nov 2026, Lukas Wunner wrote:

> On Fri, Nov 06, 2026 at 05:15:07PM +0000, sashiko-bot@kernel.org wrote:
> > > +++ b/drivers/pci/pcie/aer.c
> > > -	/*
> > > -	 * When bus ID is equal to 0, it might be a bad ID
> > > -	 * reported by Root Port.
> > > -	 */
> > > -	if ((PCI_BUS_NUM(e_info->id) != 0) &&
> > > +	/* Some Root Ports report an invalid Error Source ID */
> > > +	if (e_info->id_valid &&
> > >  	    !(dev->bus->bus_flags & PCI_BUS_FLAGS_NO_AERSID)) {
> > >  		/* Device ID match? */
> > >  		if (e_info->id == pci_dev_id(dev))
> > 
> > [Severity: Medium]
> > As reported by Ilpo Järvinen on v1 [1]
> 
> Hallucination, this was reported by sashiko itself and Ilpo merely confirmed
> sashiko's finding.

I agree. I've no problem with this change after the cases we expect this 
impact are not among the cases sashiko came up so the comment in the 
changelog is enough for me.

> > can treating pci_dev_id(root) == id
> > as unconditionally valid cause a false-positive match on the Root Port and
> > skip searching the subordinate hierarchy when a Root Port at 00:00.0 (such
> > as on DesignWare, Cadence, or Aardvark SoC host bridges) reports 0x0000 for
> > a downstream device error, or when a Root Port at 00:xx.y loses the bus
> > number of a downstream error source at bus:xx.y?
> 
> The commit message addresses this concern, it seems sashiko overlooked that
> paragraph.


-- 
 i.

  reply	other threads:[~2026-11-06 17:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-06 16:38 [PATCH v2 0/2] PCI/AER: Improve Error Source handling Lukas Wunner
2026-11-06 16:38 ` [PATCH v2 1/2] PCI/AER: Avoid NULL pointer deref on search for Error Source Lukas Wunner
2026-11-06 17:01   ` sashiko-bot
2026-11-06 16:38 ` [PATCH v2 2/2] PCI/AER: Check validity of Error Source ID register Lukas Wunner
2026-11-06 17:07   ` Ilpo Järvinen
2026-11-06 17:15   ` sashiko-bot
2026-11-06 17:25     ` Lukas Wunner
2026-11-06 17:37       ` Ilpo Järvinen [this message]
2026-11-09 23:36 ` [PATCH v2 0/2] PCI/AER: Improve Error Source handling Bjorn Helgaas

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=36c2c56c-59c4-4183-70ec-5d05e88569b5@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=sashiko-reviews@lists.linux.dev \
    /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