From: Niklas Schnelle <schnelle@linux.ibm.com>
To: Benjamin Block <bblock@linux.ibm.com>
Cc: Gerd Bayer <gbayer@linux.ibm.com>,
Matthew Rosato <mjrosato@linux.ibm.com>,
Farhan Ali <alifm@linux.ibm.com>,
Julian Ruess <julianr@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Ramesh Errabolu <ramesh@linux.ibm.com>,
Tobias Schumacher <ts@linux.ibm.com>,
Halil Pasic <pasic@linux.ibm.com>,
Peter Oberparleiter <oberpar@linux.ibm.com>,
Gerald Schaefer <gerald.schaefer@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/4] s390/pci: Fix leak of struct pci_dev reference in zpci_report_status()
Date: Mon, 21 Sep 2026 13:54:03 +0200 [thread overview]
Message-ID: <8d95a91f089186b4b09a60c24363642173263d42.camel@linux.ibm.com> (raw)
In-Reply-To: <20260918083702.GE241998@p14sgen6-pf6akexs>
On Fri, 2026-09-18 at 10:37 +0200, Benjamin Block wrote:
> On Wed, Sep 16, 2026 at 05:14:10PM +0200, Niklas Schnelle wrote:
> > diff --git a/arch/s390/pci/pci_report.c b/arch/s390/pci/pci_report.c
> > index 7030f7052926..867419779219 100644
> > --- a/arch/s390/pci/pci_report.c
> > +++ b/arch/s390/pci/pci_report.c
> > @@ -89,7 +89,8 @@ static struct debug_view debug_log_view = {
> >
> > /**
> > * zpci_report_status - Report the status of operations on a PCI device
> > - * @zdev: The PCI device for which to report status
> > + * @zdev: The zPCI device for which to report status
> > + * @pdev: The PCI device associated with the zdev if any, NULL otherwise
> > * @operation: A string representing the operation reported
> > * @status: A string representing the status of the operation
> > *
> > @@ -103,15 +104,15 @@ static struct debug_view debug_log_view = {
> > *
> > * Return: 0 on success an error code < 0 otherwise.
> > */
> > -int zpci_report_status(struct zpci_dev *zdev, const char *operation, const char *status)
> > +int zpci_report_status(struct zpci_dev *zdev, struct pci_dev *pdev,
> > + const char *operation, const char *status)
>
> One small thing that is in no way critical: I wonder whether we could make the
> `pdev` const. We don't do anything with it apart from reading some attributes
> and such.
Just checked. This conflicts with device_lock_assert() taking a non-
const struct device *. So we would have to adjust that as well.
>
> > {
> > struct zpci_report_error *report;
> > struct pci_driver *driver = NULL;
> > - struct pci_dev *pdev = NULL;
next prev parent reply other threads:[~2026-09-21 11:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 15:14 [PATCH v3 0/4] s390/pci: Fix some zpci_report_status() issues Niklas Schnelle
2026-09-16 15:14 ` [PATCH v3 1/4] s390/pci: Fix leak of struct pci_dev reference in zpci_report_status() Niklas Schnelle
2026-09-17 17:51 ` Farhan Ali
2026-09-18 8:17 ` Benjamin Block
2026-09-18 8:19 ` Niklas Schnelle
2026-09-18 8:20 ` Benjamin Block
2026-09-18 8:37 ` Benjamin Block
2026-09-21 11:54 ` Niklas Schnelle [this message]
2026-09-16 15:14 ` [PATCH v3 2/4] s390/pci: Fix missing device lock " Niklas Schnelle
2026-09-17 17:52 ` Farhan Ali
2026-09-18 8:26 ` Benjamin Block
2026-09-16 15:14 ` [PATCH v3 3/4] s390/pci: Report SCLP status on error events when no pdev is associated Niklas Schnelle
2026-09-17 18:06 ` Farhan Ali
2026-09-18 8:32 ` Benjamin Block
2026-09-16 15:14 ` [PATCH v3 4/4] s390/pci: Don't report recovery success on skipped recovery Niklas Schnelle
2026-09-17 18:08 ` Farhan Ali
2026-09-18 8:34 ` Benjamin Block
2026-09-21 12:58 ` [PATCH v3 0/4] s390/pci: Fix some zpci_report_status() issues Heiko Carstens
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=8d95a91f089186b4b09a60c24363642173263d42.camel@linux.ibm.com \
--to=schnelle@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=alifm@linux.ibm.com \
--cc=bblock@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gbayer@linux.ibm.com \
--cc=gerald.schaefer@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=julianr@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mjrosato@linux.ibm.com \
--cc=oberpar@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=ramesh@linux.ibm.com \
--cc=svens@linux.ibm.com \
--cc=ts@linux.ibm.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
all inboxes | Powered by JetHome®