From: sashiko-bot@kernel.org
To: "Dave Marquardt" <davemarq@linux.ibm.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH v18 10/13] scsi: ibmvfc: add interrupt routine for asynchronous sub CRQ
Date: Thu, 05 Nov 2026 18:37:18 +0000 [thread overview]
Message-ID: <sashiko-outbox-199779@kernel.org> (raw)
In-Reply-To: <20261105-ibmvfc-fpin-support-v18-10-d683b74736a3@linux.ibm.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [High] scsi: ibmvfc: NULL crq dereference in ibmvfc_process_async_work()
- [High] scsi: ibmvfc: uninitialized tgt pointer in ibmvfc_process_async_work()
--
commit e623a6d56430928cd690d92425a90ffd4dc7ba74
Author: Dave Marquardt <davemarq@linux.ibm.com>
scsi: ibmvfc: add interrupt routine for asynchronous sub CRQ
This commit adds ibmvfc_interrupt_async_subq() and supporting helpers to
drain asynchronous sub-CRQ entries onto a temporary list and dispatch them
through ibmvfc_handle_async().
> diff --git a/drivers/scsi/ibmvscsi/ibmvfc-core.c b/drivers/scsi/ibmvscsi/ibmvfc-core.c
> index 7406e7182777c..5dba084086d5f 100644
> --- a/drivers/scsi/ibmvscsi/ibmvfc-core.c
> +++ b/drivers/scsi/ibmvscsi/ibmvfc-core.c
> @@ -4456,6 +4456,106 @@ static struct ibmvfc_crq *ibmvfc_next_scrq(struct ibmvfc_queue *scrq)
[ ... ]
> +static void ibmvfc_queue_async_subq_entry(struct ibmvfc_host *vhost,
> + struct ibmvfc_async_sub_crq *crq,
> + struct list_head *doneq)
> +{
> + struct ibmvfc_async_drain_entry *entry;
> +
> + entry = kzalloc_obj(*entry, GFP_ATOMIC);
> + if (entry) {
> + entry->event.type = IBMVFC_ASYNC_CRQ_SUB;
> + entry->event.subq = *crq;
[Severity: High]
Can dispatching an IBMVFC_ASYNC_CRQ_SUB FPIN event here lead to a NULL
pointer dereference in ibmvfc_process_async_work()?
When ibmvfc_drain_async_subq() passes entry->event to ibmvfc_handle_async()
for an IBMVFC_AE_FPIN event, it queues ibmvfc_process_async_work() with
aw->event.type == IBMVFC_ASYNC_CRQ_SUB.
In drivers/scsi/ibmvscsi/ibmvfc-core.c:ibmvfc_process_async_work(), crq is
initialized to NULL and remains NULL on the IBMVFC_ASYNC_CRQ_SUB branch:
struct ibmvfc_async_sub_crq *subq = NULL;
struct ibmvfc_async_work *aw;
struct ibmvfc_async_crq *crq = NULL;
...
if (aw->event.type == IBMVFC_ASYNC_CRQ_SUB) {
subq = &aw->event.subq;
scsi_id = 0;
wwpn = subq->wwpn;
...
}
If the sub-CRQ FPIN event has all-zero target identifiers (for example, a
host-scope IBMVFC_AE_FPIN_LINK_CONGESTED or
IBMVFC_AE_FPIN_CONGESTION_CLEARED event with zero wwpn and zero
node_name/assoc_id, or with IBMVFC_ASYNC_IS_FPIN_EXT set and wwpn == 0),
ibmvfc_process_async_work() unconditionally calls ibmvfc_basic_fpin_to_desc()
with crq == NULL instead of ibmvfc_full_fpin_to_desc(subq, ...):
if (!scsi_id && !wwpn && !node_name && !assoc_id) {
if (fpin_status == IBMVFC_AE_FPIN_LINK_CONGESTED ||
fpin_status == IBMVFC_AE_FPIN_CONGESTION_CLEARED)
fpin = ibmvfc_basic_fpin_to_desc(crq,
cpu_to_be64(fc_host_port_name(vhost->host)), 0);
goto send_fpin;
}
ibmvfc_basic_fpin_to_desc() then immediately dereferences crq->fpin_status.
Should this path check if (crq) vs else ibmvfc_full_fpin_to_desc(subq, ...)
in the same way as the !tgt fallback below it?
> + list_add_tail(&entry->list, doneq);
> + } else
> + dev_err_ratelimited(vhost->dev,
> + "Couldn't allocate async drain entry\n");
> + crq->valid = 0;
> + wmb(); /* complete write */
> +}
> +
> +static void ibmvfc_drain_async_subq(struct ibmvfc_queue *scrq)
> +{
[ ... ]
> + list_for_each_entry_safe(entry, temp, &doneq, list) {
> + list_del(&entry->list);
> + spin_lock_irqsave(&vhost->host->host_lock, flags);
> + ibmvfc_handle_async(&entry->event, vhost);
[Severity: High]
When ibmvfc_handle_async() queues ibmvfc_process_async_work() for an
IBMVFC_AE_FPIN event with all-zero target identifiers, can tgt be used
uninitialized at the send_fpin label?
In drivers/scsi/ibmvscsi/ibmvfc-core.c:ibmvfc_process_async_work(), tgt is
declared without initialization, and the all-zero identifier check jumps
over ibmvfc_find_target() directly to send_fpin:
struct ibmvfc_target *tgt;
...
if (!scsi_id && !wwpn && !node_name && !assoc_id) {
if (fpin_status == IBMVFC_AE_FPIN_LINK_CONGESTED ||
fpin_status == IBMVFC_AE_FPIN_CONGESTION_CLEARED)
fpin = ibmvfc_basic_fpin_to_desc(crq,
cpu_to_be64(fc_host_port_name(vhost->host)), 0);
goto send_fpin;
}
...
send_fpin:
...
if (tgt)
kref_put(&tgt->kref, ibmvfc_release_tgt);
Wouldn't that evaluate if (tgt) and call kref_put() on an uninitialized
stack pointer?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261105-ibmvfc-fpin-support-v18-0-d683b74736a3@linux.ibm.com?part=10
next prev parent reply other threads:[~2026-11-05 18:37 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 17:22 [PATCH v18 00/13] scsi: ibmvfc: make ibmvfc support FPIN messages Dave Marquardt via B4 Relay
2026-11-05 17:22 ` Dave Marquardt
2026-11-05 17:22 ` [PATCH v18 01/13] scsi: ibmvfc: fix IRQ leak and guard deregister on channel reg failure Dave Marquardt via B4 Relay
2026-11-05 17:22 ` Dave Marquardt
2026-11-05 17:22 ` [PATCH v18 02/13] scsi: ibmvfc: fix potential clobbering of rc after failed irq setup Dave Marquardt via B4 Relay
2026-11-05 17:22 ` Dave Marquardt
2026-11-05 17:22 ` [PATCH v18 03/13] scsi: ibmvfc: fix potential NULL pointer dereference on failed queue allocation Dave Marquardt via B4 Relay
2026-11-05 17:22 ` Dave Marquardt
2026-11-05 17:22 ` [PATCH v18 04/13] scsi: ibmvfc: fix stale rc and IRQ mapping leak in ibmvfc_register_channel() Dave Marquardt
2026-11-05 17:22 ` Dave Marquardt via B4 Relay
2026-11-05 17:22 ` [PATCH v18 05/13] scsi: ibmvfc: fix resource leaks on partial queue allocation failure Dave Marquardt via B4 Relay
2026-11-05 17:22 ` Dave Marquardt
2026-11-05 18:00 ` sashiko-bot
2026-11-05 20:55 ` Dave Marquardt
2026-11-05 17:22 ` [PATCH v18 06/13] scsi: ibmvfc: add basic FPIN support Dave Marquardt via B4 Relay
2026-11-05 17:22 ` Dave Marquardt
2026-11-05 18:09 ` sashiko-bot
2026-11-05 21:09 ` Dave Marquardt
2026-11-05 17:23 ` [PATCH v18 07/13] scsi: ibmvfc: add NOOP command support Dave Marquardt via B4 Relay
2026-11-05 17:23 ` Dave Marquardt
2026-11-05 17:23 ` [PATCH v18 08/13] scsi: ibmvfc: add FPIN extended flag and async sub-CRQ queue handle Dave Marquardt via B4 Relay
2026-11-05 17:23 ` Dave Marquardt
2026-11-05 17:23 ` [PATCH v18 09/13] scsi: ibmvfc: extend async event handlers for async sub-CRQ events Dave Marquardt
2026-11-05 17:23 ` Dave Marquardt via B4 Relay
2026-11-05 18:25 ` sashiko-bot
2026-11-05 22:24 ` Dave Marquardt
2026-11-05 17:23 ` [PATCH v18 10/13] scsi: ibmvfc: add interrupt routine for asynchronous sub CRQ Dave Marquardt via B4 Relay
2026-11-05 17:23 ` Dave Marquardt
2026-11-05 18:37 ` sashiko-bot [this message]
2026-11-05 22:28 ` Dave Marquardt
2026-11-05 17:23 ` [PATCH v18 11/13] scsi: ibmvfc: extend channel registration for async sub-CRQ Dave Marquardt via B4 Relay
2026-11-05 17:23 ` Dave Marquardt
2026-11-05 17:23 ` [PATCH v18 12/13] scsi: ibmvfc: register and use asynchronous sub CRQ for events Dave Marquardt via B4 Relay
2026-11-05 17:23 ` Dave Marquardt
2026-11-05 19:03 ` sashiko-bot
2026-11-09 17:29 ` Dave Marquardt
2026-11-05 17:23 ` [PATCH v18 13/13] scsi: ibmvfc: handle extended FPIN events Dave Marquardt via B4 Relay
2026-11-05 17:23 ` Dave Marquardt
2026-11-05 19:15 ` sashiko-bot
2026-11-11 18:01 ` Dave Marquardt
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=sashiko-outbox-199779@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=davemarq@linux.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.