From: Dave Marquardt <davemarq@linux.ibm.com>
To: sashiko-reviews@lists.linux.dev
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH v7 1/8] scsi: ibmvfc: add basic FPIN support
Date: Wed, 02 Sep 2026 16:59:55 -0500 [thread overview]
Message-ID: <87h5k71fhg.fsf@linux.ibm.com> (raw)
In-Reply-To: <20260831213004.085A21F000E9@smtp.kernel.org>
sashiko-bot@kernel.org writes:
> Thank you for your contribution! Sashiko AI review found 3 potential issue(s) to consider:
> - [High] Teardown ordering race allows FPIN works to execute on an unregistered `fc_host`.
> - [Medium] Lockless traversal of global `ibmvfc_head` list in KUnit test risks use-after-free.
> - [Medium] The KUnit test accesses `tgt->rport` outside of the `host_lock`.
> --
>
> commit 6a259111a28ef932ad14496cabbef71084312dfe
> Author: Dave Marquardt <davemarq@linux.ibm.com>
>
> scsi: ibmvfc: add basic FPIN support
>
> Implement support for a basic level of Fabric Performance Impact
> Notifications (FPIN) in the ibmvfc driver to enable monitoring of
> fabric congestion and link integrity events. Offloads FPIN processing
> to a dedicated workqueue and adds a KUnit test module for validation.
>
>> diff --git a/drivers/scsi/ibmvscsi/ibmvfc_kunit.c b/drivers/scsi/ibmvscsi/ibmvfc_kunit.c
>> new file mode 100644
>> index 0000000000000..8a73ea1b1da8c
>> --- /dev/null
>> +++ b/drivers/scsi/ibmvscsi/ibmvfc_kunit.c
> [ ... ]
>> @@ -0,0 +1,146 @@
> [ ... ]
>> +static void ibmvfc_async_fpin_test(struct kunit *test)
>> +{
> [ ... ]
>> + headp = ibmvfc_get_headp();
>> + if (list_empty(headp))
>> + kunit_skip(test, "No ibmvfc devices available");
>> + queue = headp->next;
>> + vhost = container_of_const(queue, struct ibmvfc_host, queue);
>
> [Severity: Medium]
> Could this lockless traversal of the global ibmvfc_head list lead to a
> use-after-free regression?
>
> If ibmvfc_remove() executes concurrently (for instance, during a device
> hot-unplug), it could remove and free the vhost structure while the KUnit test
> is still traversing the list.
Yes, this is a potential problem. I'll be using a new routine to get the
first vhost that's referenced with scsi_host_get(), or NULL. The callers
(tests) then must use scsi_host_put() before returning.
>> +
>> + spin_lock_irqsave(vhost->host->host_lock, flags);
>> + if (vhost->scsi_scrqs.num_targets < 1) {
>> + spin_unlock_irqrestore(vhost->host->host_lock, flags);
>> + kunit_skip(test, "No targets");
>> + }
>> + tgt = list_first_entry(&vhost->scsi_scrqs.targets, struct ibmvfc_target, queue);
>> + if (!tgt->rport) {
>> + spin_unlock_irqrestore(vhost->host->host_lock, flags);
>> + kunit_skip(test, "No rport");
>> + }
>> + kref_get(&tgt->kref);
>> + spin_unlock_irqrestore(vhost->host->host_lock, flags);
>> +
>> + fc_host = shost_to_fc_host(vhost->host);
>> +
>> + pre[IBMVFC_AE_FPIN_LINK_CONGESTED] = READ_ONCE(fc_host->fpin_stats.cn_device_specific);
>> + pre[IBMVFC_AE_FPIN_PORT_CONGESTED] = READ_ONCE(tgt->rport->fpin_stats.cn_device_specific);
>
> [Severity: Medium]
> Is there a potential use-after-free regression here if tgt->rport is
> dereferenced outside of the host_lock?
>
> The test grabs a reference to tgt and drops vhost->host->host_lock, but then
> reads tgt->rport->fpin_stats locklessly. If an event like a link down triggers
> ibmvfc_del_tgt() concurrently, it can schedule the removal of the remote port.
> The worker thread would then call fc_remote_port_delete(rport), freeing the
> rport while the test is still dereferencing it.
Yes, this is another problem. I'll be adding device references to the
rport in the tests.
-Dave
next prev parent reply other threads:[~2026-09-02 22:00 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 19:00 [PATCH v7 0/8] scsi: ibmvfc: make ibmvfc support FPIN messages Dave Marquardt via B4 Relay
2026-08-31 19:00 ` Dave Marquardt
2026-08-31 19:00 ` [PATCH v7 1/8] scsi: ibmvfc: add basic FPIN support Dave Marquardt via B4 Relay
2026-08-31 19:00 ` Dave Marquardt
2026-08-31 21:30 ` sashiko-bot
2026-09-02 20:29 ` Dave Marquardt
2026-09-02 21:59 ` Dave Marquardt [this message]
2026-08-31 19:00 ` [PATCH v7 2/8] scsi: ibmvfc: Add NOOP command support Dave Marquardt via B4 Relay
2026-08-31 19:00 ` Dave Marquardt
2026-08-31 21:40 ` sashiko-bot
2026-09-03 15:08 ` Dave Marquardt
2026-08-31 19:00 ` [PATCH v7 3/8] scsi: ibmvfc: add FPIN extended flag and async sub-CRQ queue handle Dave Marquardt via B4 Relay
2026-08-31 19:00 ` Dave Marquardt
2026-08-31 19:00 ` [PATCH v7 4/8] scsi: ibmvfc: extend async event handlers to handle async sub queue events Dave Marquardt via B4 Relay
2026-08-31 19:00 ` Dave Marquardt
2026-08-31 19:00 ` [PATCH v7 5/8] scsi: ibmvfc: add interrupt routine for asynchronous sub CRQ Dave Marquardt via B4 Relay
2026-08-31 19:00 ` Dave Marquardt
2026-08-31 22:18 ` sashiko-bot
2026-09-03 16:18 ` Dave Marquardt
2026-08-31 19:00 ` [PATCH v7 6/8] scsi: ibmvfc: extend channel registration and deregistration for async subq Dave Marquardt via B4 Relay
2026-08-31 19:00 ` Dave Marquardt
2026-08-31 22:34 ` sashiko-bot
2026-09-03 18:43 ` Dave Marquardt
2026-08-31 19:00 ` [PATCH v7 7/8] scsi: ibmvfc: register and use asynchronous sub CRQ for events Dave Marquardt via B4 Relay
2026-08-31 19:00 ` Dave Marquardt
2026-08-31 22:46 ` sashiko-bot
2026-09-08 19:52 ` Dave Marquardt
2026-08-31 19:00 ` [PATCH v7 8/8] scsi: ibmvfc: handle extended FPIN events Dave Marquardt via B4 Relay
2026-08-31 19:00 ` Dave Marquardt
2026-08-31 22:56 ` sashiko-bot
2026-09-08 19:53 ` 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=87h5k71fhg.fsf@linux.ibm.com \
--to=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.