From: Heiko Carstens <hca@linux.ibm.com>
To: Alexander Gordeev <agordeev@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Niklas Schnelle <schnelle@linux.ibm.com>,
Gerd Bayer <gbayer@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 2/3] s390/pci: Rework__zpci_event_availability() to remove conditional locking
Date: Mon, 3 Aug 2026 12:07:22 +0200 [thread overview]
Message-ID: <20260803100723.2343688-3-hca@linux.ibm.com> (raw)
In-Reply-To: <20260803100723.2343688-1-hca@linux.ibm.com>
Clang's compiler based static context analysis does not work with locks
that are conditionally taken like in __zpci_event_availability():
arch/s390/pci/pci_event.c:402:10: warning: mutex 'get_zdev_by_fid(ccdf->fid).state_lock'
is not held on every path through here [-Wthread-safety-analysis]
Given that code which takes locks conditionally can be considered
suboptimal rework __zpci_event_availability() to get rid of this.
Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
---
arch/s390/pci/pci_event.c | 103 ++++++++++++++++++--------------------
1 file changed, 49 insertions(+), 54 deletions(-)
diff --git a/arch/s390/pci/pci_event.c b/arch/s390/pci/pci_event.c
index 48fa26dcbee1..37acee2c7d25 100644
--- a/arch/s390/pci/pci_event.c
+++ b/arch/s390/pci/pci_event.c
@@ -390,18 +390,21 @@ static void zpci_event_reappear(struct zpci_dev *zdev)
static void __zpci_event_availability(struct zpci_ccdf_avail *ccdf)
{
struct zpci_dev *zdev = get_zdev_by_fid(ccdf->fid);
- bool existing_zdev = !!zdev;
enum zpci_state state;
zpci_dbg(3, "avl fid:%x, fh:%x, pec:%x\n",
ccdf->fid, ccdf->fh, ccdf->pec);
- if (existing_zdev)
- mutex_lock(&zdev->state_lock);
+ if (ccdf->pec == 0x0306) {
+ /* 0x308 or 0x302 for multiple devices */
+ zpci_remove_reserved_devices();
+ zpci_scan_devices();
+ return;
+ }
- switch (ccdf->pec) {
- case 0x0301: /* Reserved|Standby -> Configured */
- if (!zdev) {
+ if (!zdev) {
+ switch (ccdf->pec) {
+ case 0x0301: /* Reserved|Standby -> Configured */
zdev = zpci_create_device(ccdf->fid, ccdf->fh, ZPCI_FN_STATE_CONFIGURED);
if (IS_ERR(zdev))
break;
@@ -409,18 +412,9 @@ static void __zpci_event_availability(struct zpci_ccdf_avail *ccdf)
kfree(zdev);
break;
}
- } else {
- if (zdev->state == ZPCI_FN_STATE_RESERVED)
- zpci_event_reappear(zdev);
- /* the configuration request may be stale */
- else if (zdev->state != ZPCI_FN_STATE_STANDBY)
- break;
- zdev->state = ZPCI_FN_STATE_CONFIGURED;
- }
- zpci_scan_configured_device(zdev, ccdf->fh);
- break;
- case 0x0302: /* Reserved -> Standby */
- if (!zdev) {
+ zpci_scan_configured_device(zdev, ccdf->fh);
+ break;
+ case 0x0302: /* Reserved -> Standby */
zdev = zpci_create_device(ccdf->fid, ccdf->fh, ZPCI_FN_STATE_STANDBY);
if (IS_ERR(zdev))
break;
@@ -428,53 +422,54 @@ static void __zpci_event_availability(struct zpci_ccdf_avail *ccdf)
kfree(zdev);
break;
}
- } else {
- if (zdev->state == ZPCI_FN_STATE_RESERVED)
- zpci_event_reappear(zdev);
- zpci_update_fh(zdev, ccdf->fh);
+ break;
}
+ return;
+ }
+
+ mutex_lock(&zdev->state_lock);
+ switch (ccdf->pec) {
+ case 0x0301: /* Reserved|Standby -> Configured */
+ if (zdev->state == ZPCI_FN_STATE_RESERVED)
+ zpci_event_reappear(zdev);
+ /* the configuration request may be stale */
+ else if (zdev->state != ZPCI_FN_STATE_STANDBY)
+ break;
+ zdev->state = ZPCI_FN_STATE_CONFIGURED;
+ zpci_scan_configured_device(zdev, ccdf->fh);
+ break;
+ case 0x0302: /* Reserved -> Standby */
+ if (zdev->state == ZPCI_FN_STATE_RESERVED)
+ zpci_event_reappear(zdev);
+ zpci_update_fh(zdev, ccdf->fh);
break;
case 0x0303: /* Deconfiguration requested */
- if (zdev) {
- /* The event may have been queued before we configured
- * the device.
- */
- if (zdev->state != ZPCI_FN_STATE_CONFIGURED)
- break;
- zpci_update_fh(zdev, ccdf->fh);
- zpci_deconfigure_device(zdev);
- }
+ /* The event may have been queued before we configured
+ * the device.
+ */
+ if (zdev->state != ZPCI_FN_STATE_CONFIGURED)
+ break;
+ zpci_update_fh(zdev, ccdf->fh);
+ zpci_deconfigure_device(zdev);
break;
case 0x0304: /* Configured -> Standby|Reserved */
- if (zdev) {
- /* The event may have been queued before we configured
- * the device.:
- */
- if (zdev->state == ZPCI_FN_STATE_CONFIGURED)
- zpci_event_hard_deconfigured(zdev, ccdf->fh);
- /* The 0x0304 event may immediately reserve the device */
- if (!clp_get_state(zdev->fid, &state) &&
- state == ZPCI_FN_STATE_RESERVED) {
- zpci_device_reserved(zdev);
- }
+ /* The event may have been queued before we configured
+ * the device.:
+ */
+ if (zdev->state == ZPCI_FN_STATE_CONFIGURED)
+ zpci_event_hard_deconfigured(zdev, ccdf->fh);
+ /* The 0x0304 event may immediately reserve the device */
+ if (!clp_get_state(zdev->fid, &state) &&
+ state == ZPCI_FN_STATE_RESERVED) {
+ zpci_device_reserved(zdev);
}
break;
- case 0x0306: /* 0x308 or 0x302 for multiple devices */
- zpci_remove_reserved_devices();
- zpci_scan_devices();
- break;
case 0x0308: /* Standby -> Reserved */
- if (!zdev)
- break;
zpci_device_reserved(zdev);
break;
- default:
- break;
- }
- if (existing_zdev) {
- mutex_unlock(&zdev->state_lock);
- zpci_zdev_put(zdev);
}
+ mutex_unlock(&zdev->state_lock);
+ zpci_zdev_put(zdev);
}
void zpci_event_availability(void *data)
--
2.53.0
next prev parent reply other threads:[~2026-08-03 10:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 10:07 [PATCH 0/3] s390/pci: Enable CONTEXT_ANALYSIS Heiko Carstens
2026-08-03 10:07 ` [PATCH 1/3] s390/pci: Rework __zpci_event_error() to remove conditional locking Heiko Carstens
2026-08-03 10:12 ` sashiko-bot
2026-08-03 10:07 ` Heiko Carstens [this message]
2026-08-03 10:17 ` [PATCH 2/3] s390/pci: Rework__zpci_event_availability() " sashiko-bot
2026-08-03 11:29 ` Heiko Carstens
2026-08-03 10:07 ` [PATCH 3/3] s390/pci: Enable CONTEXT_ANALYSIS Heiko Carstens
2026-08-03 10:13 ` sashiko-bot
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=20260803100723.2343688-3-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gbayer@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=schnelle@linux.ibm.com \
--cc=svens@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