public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: "Musham, Sai Krishna" <sai.krishna.musham@amd.com>
Cc: Rakuram Eswaran <rakuram.e96@gmail.com>,
	"lpieralisi@kernel.org" <lpieralisi@kernel.org>,
	"kwilczynski@kernel.org" <kwilczynski@kernel.org>,
	"mani@kernel.org" <mani@kernel.org>,
	"robh@kernel.org" <robh@kernel.org>,
	"bhelgaas@google.com" <bhelgaas@google.com>,
	"lkp@intel.com" <lkp@intel.com>,
	"error27@gmail.com" <error27@gmail.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"jirislaby@kernel.org" <jirislaby@kernel.org>,
	"Havalige, Thippeswamy" <thippeswamy.havalige@amd.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Dan Carpenter <dan.carpenter@linaro.org>
Subject: Re: [PATCH] PCI: amd-mdb: fix incorrect IRQ number in INTx error message
Date: Sat, 24 Jan 2026 14:25:30 -0600	[thread overview]
Message-ID: <20260124202530.GA175580@bhelgaas> (raw)
In-Reply-To: <IA4PR12MB9810A988D4192F92AB760CECCD95A@IA4PR12MB9810.namprd12.prod.outlook.com>

On Sat, Jan 24, 2026 at 02:02:51PM +0000, Musham, Sai Krishna wrote:
> [AMD Official Use Only - AMD Internal Distribution Only]
> 
> Hi Rakuram,
> 
> > -----Original Message-----
> > From: Rakuram Eswaran <rakuram.e96@gmail.com>
> > Sent: Wednesday, December 24, 2025 12:10 AM
> > To: lpieralisi@kernel.org; kwilczynski@kernel.org; mani@kernel.org;
> > robh@kernel.org; bhelgaas@google.com
> > Cc: lkp@intel.com; error27@gmail.com; Musham, Sai Krishna
> > <sai.krishna.musham@amd.com>; tglx@linutronix.de; jirislaby@kernel.org;
> > Havalige, Thippeswamy <thippeswamy.havalige@amd.com>; linux-
> > pci@vger.kernel.org; linux-kernel@vger.kernel.org; Rakuram Eswaran
> > <rakuram.e96@gmail.com>; Dan Carpenter <dan.carpenter@linaro.org>
> > Subject: [PATCH] PCI: amd-mdb: fix incorrect IRQ number in INTx error message
> >
> > Caution: This message originated from an External Source. Use proper caution
> > when opening attachments, clicking links, or responding.
> >
> >
> > The INTx devm_request_irq() failure path logs an incorrect IRQ
> > number. The printed 'irq' variable refers to a previous MDB
> > interrupt mapping and does not correspond to the INTx IRQ being
> > requested.
> >
> > Fix the error message to report pcie->intx_irq, which is the IRQ
> > associated with the failing request.
> >
> > Reported-by: kernel test robot <lkp@intel.com>
> > Reported-by: Dan Carpenter <dan.carpenter@linaro.org>
> > Closes: https://lore.kernel.org/r/202512230112.AaiGqMWM-lkp@intel.com/
> > Signed-off-by: Rakuram Eswaran <rakuram.e96@gmail.com>
> > ---
> > Testing note:
> > Compile-tested only.
> >
> > Static analysis was performed with Smatch to ensure the reported warning
> > no longer reproduces after applying this fix.
> >
> > Command using for testing:
> > ~/project/smatch/smatch_scripts/kchecker ./drivers/pci/controller/dwc/pcie-amd-
> > mdb.c
> >
> >  drivers/pci/controller/dwc/pcie-amd-mdb.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/pci/controller/dwc/pcie-amd-mdb.c b/drivers/pci/controller/dwc/pcie-
> > amd-mdb.c
> > index 3c6e837465bb..7e50e11fbffd 100644
> > --- a/drivers/pci/controller/dwc/pcie-amd-mdb.c
> > +++ b/drivers/pci/controller/dwc/pcie-amd-mdb.c
> > @@ -389,7 +389,7 @@ static int amd_mdb_setup_irq(struct amd_mdb_pcie *pcie,
> >                                IRQF_NO_THREAD, NULL, pcie);
> >         if (err) {
> >                 dev_err(dev, "Failed to request INTx IRQ %d, err=%d\n",
> > -                       irq, err);
> > +                       pcie->intx_irq, err);
> 
> The fix is correct. The `irq` variable at that point contains the last
> IRQ mapped in the preceding for loop (an MDB event IRQ), not the INTx
> IRQ being requested via devm_request_irq(). Using `pcie->intx_irq`
> accurately reports the failing IRQ number.
> 
> Thanks,
> Sai Krishna

Sai, if you include a "Reviewed-by: Sai Krishna <email-addr>", we can
add that when merging the fix.  It sounds like that's your intent, but
I don't want to presume.

  reply	other threads:[~2026-01-24 20:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-23 18:40 [PATCH] PCI: amd-mdb: fix incorrect IRQ number in INTx error message Rakuram Eswaran
2026-01-12 17:21 ` Rakuram Eswaran
2026-01-24 14:02 ` Musham, Sai Krishna
2026-01-24 20:25   ` Bjorn Helgaas [this message]
2026-01-27  9:04 ` Musham, Sai Krishna
2026-02-26  6:00 ` Manivannan Sadhasivam

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=20260124202530.GA175580@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=dan.carpenter@linaro.org \
    --cc=error27@gmail.com \
    --cc=jirislaby@kernel.org \
    --cc=kwilczynski@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=lpieralisi@kernel.org \
    --cc=mani@kernel.org \
    --cc=rakuram.e96@gmail.com \
    --cc=robh@kernel.org \
    --cc=sai.krishna.musham@amd.com \
    --cc=tglx@linutronix.de \
    --cc=thippeswamy.havalige@amd.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