From: Adriano Cordova <adrianox@gmail.com>
To: Madhavan Srinivasan <maddy@linux.ibm.com>,
Tyrel Datwyler <tyreld@linux.ibm.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <chleroy@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Linas Vepstas <linas@austin.ibm.com>,
linuxppc-dev@lists.ozlabs.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org,
Adriano Cordova <adrianox@gmail.com>
Subject: [PATCH] PCI: rpaphp: report first slot registration error
Date: Thu, 10 Sep 2026 09:13:30 -0300 [thread overview]
Message-ID: <20260910121330.339150-1-adrianox@gmail.com> (raw)
rpaphp_drc_add_slot() overwrites retval on every loop iteration, so a
failure to register a slot is lost if a later slot registers
successfully and the function returns success.
Track the first error and return it, while still attempting to register
the remaining slots.
Signed-off-by: Adriano Cordova <adrianox@gmail.com>
---
drivers/pci/hotplug/rpaphp_core.c | 11 +++++++----
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/drivers/pci/hotplug/rpaphp_core.c b/drivers/pci/hotplug/rpaphp_core.c
index 2316de0fd198..af7241d526cf 100644
--- a/drivers/pci/hotplug/rpaphp_core.c
+++ b/drivers/pci/hotplug/rpaphp_core.c
@@ -376,6 +376,7 @@ static int rpaphp_drc_add_slot(struct device_node *dn)
{
struct slot *slot;
int retval = 0;
+ int first_error = 0;
int i;
const __be32 *indexes, *names, *types, *power_domains;
char *name, *type;
@@ -407,16 +408,18 @@ static int rpaphp_drc_add_slot(struct device_node *dn)
if (!retval)
retval = rpaphp_register_slot(slot);
- if (retval)
+ if (retval) {
+ if (!first_error)
+ first_error = retval;
dealloc_slot_struct(slot);
+ }
name += strlen(name) + 1;
type += strlen(type) + 1;
}
- dbg("%s - Exit: rc[%d]\n", __func__, retval);
+ dbg("%s - Exit: rc[%d]\n", __func__, first_error);
- /* XXX FIXME: reports a failure only if last entry in loop failed */
- return retval;
+ return first_error;
}
/**
--
2.51.0
reply other threads:[~2026-09-10 12:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260910121330.339150-1-adrianox@gmail.com \
--to=adrianox@gmail.com \
--cc=bhelgaas@google.com \
--cc=chleroy@kernel.org \
--cc=linas@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=tyreld@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®