[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240703081247.GA4117643@rocinante>
Date: Wed, 3 Jul 2024 17:12:47 +0900
From: Krzysztof WilczyĆski <kw@...ux.com>
To: Wei Liu <wei.liu@...nel.org>
Cc: Linux on Hyper-V List <linux-hyperv@...r.kernel.org>, stable@...nel.org,
Michael Kelley <mhklinux@...look.com>,
"K. Y. Srinivasan" <kys@...rosoft.com>,
Haiyang Zhang <haiyangz@...rosoft.com>,
Dexuan Cui <decui@...rosoft.com>,
Lorenzo Pieralisi <lpieralisi@...nel.org>,
Rob Herring <robh@...nel.org>, Bjorn Helgaas <bhelgaas@...gle.com>,
Jake Oshins <jakeo@...rosoft.com>,
"open list:PCI NATIVE HOST BRIDGE AND ENDPOINT DRIVERS" <linux-pci@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3] PCI: hv: Return zero, not garbage, when reading
PCI_INTERRUPT_PIN
Hello,
> > The intent of the code snippet is to always return 0 for both
> > PCI_INTERRUPT_LINE and PCI_INTERRUPT_PIN.
> >
> > The check misses PCI_INTERRUPT_PIN. This patch fixes that.
> >
> > This is discovered by this call in VFIO:
> >
> > pci_read_config_byte(vdev->pdev, PCI_INTERRUPT_PIN, &pin);
> >
> > The old code does not set *val to 0 because it misses the check for
> > PCI_INTERRUPT_PIN. Garbage is returned in that case.
[...]
>
> Bjorn & other PCI maintainers, do you want to pick this up via your
> tree?
>
> I can pick this up via the hyperv tree if you prefer.
We will pick this up. No worries.
Krzysztof
Powered by blists - more mailing lists