From: Tyrel Datwyler <tyreld@linux.ibm.com>
To: sashiko-reviews@lists.linux.dev
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH v9 5/9] scsi: ibmvfc: add interrupt routine for asynchronous sub CRQ
Date: Thu, 10 Sep 2026 20:53:38 -0700 [thread overview]
Message-ID: <6db82d74-2251-416b-8a29-7caa9301c2c5@linux.ibm.com> (raw)
In-Reply-To: <20260911024419.047191F000FF@smtp.kernel.org>
On 9/10/26 7:44 PM, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Low] Missing address-of operator (`&`) when referencing `Scsi_Host`'s `host_lock`, causing a fatal compilation error.
> --
>
> commit af3cb177b633d7c7bd704888c846393f549edaef
> Author: Dave Marquardt <davemarq@linux.ibm.com>
> Date: Fri Sep 11 02:19:05 2026 +0000
>
> scsi: ibmvfc: add interrupt routine for asynchronous sub CRQ
>
> This commit adds an interrupt routine and a draining function for asynchronous
> sub-CRQ events. It handles disabling and enabling IRQs to process entries
> while holding the queue and host locks.
>
>> diff --git a/drivers/scsi/ibmvscsi/ibmvfc-core.c b/drivers/scsi/ibmvscsi/ibmvfc-core.c
>> index daec81f48857d..553fca31cb3aa 100644
>> --- a/drivers/scsi/ibmvscsi/ibmvfc-core.c
>> +++ b/drivers/scsi/ibmvscsi/ibmvfc-core.c
>
> [ ... ]
>
>> @@ -4376,6 +4376,60 @@ static struct ibmvfc_crq *ibmvfc_next_scrq(struct ibmvfc_queue *scrq)
>> return crq;
>> }
>>
>> +static void ibmvfc_drain_async_subq(struct ibmvfc_queue *scrq)
>> +{
>> + struct ibmvfc_host *vhost = scrq->vhost;
>> + unsigned long flags;
>> + struct ibmvfc_crq *crq;
>> + int done = 0;
>> +
>> + spin_lock_irqsave(vhost->host->host_lock, flags);
>
> [Severity: Low]
> Does this code need an address-of operator for host_lock?
>
> Since kernel 5.14, the Scsi_Host's host_lock field is an embedded spinlock_t
> struct, so passing it directly to spin_lock_irqsave causes it to be passed
> by value. This regression will result in a compilation error because the
> lock function expects a pointer to a spinlock_t.
>
> Would it make sense to also update ibmvfc_process_async_work, as well as
> ibmvfc_async_fpin_test and ibmvfc_full_fpin_test in the KUnit tests, which
> appear to have this same pattern introduced earlier in the series?
>
>> + spin_lock(scrq->q_lock);
>> + while (!done) {
>
> [ ... ]
>
>> + } else
>> + done = 1;
>> + }
>> + spin_unlock(scrq->q_lock);
>> + spin_unlock_irqrestore(vhost->host->host_lock, flags);
>
> [Severity: Low]
> Similar to the lock acquisition above, does spin_unlock_irqrestore also
> need an address-of operator to pass a pointer to host_lock?
>
>> +}
>
Again, as noted in patch 1 this breaks the build. Will fix in v10.
-Tyrel
next prev parent reply other threads:[~2026-09-11 3:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 2:19 [PATCH v9 0/9] scsi: ibmvfc: make ibmvfc support FPIN messages Tyrel Datwyler
2026-09-11 2:19 ` [PATCH v9 1/9] scsi: ibmvfc: add basic FPIN support Tyrel Datwyler
2026-09-11 2:38 ` sashiko-bot
2026-09-11 3:40 ` Tyrel Datwyler
2026-09-11 2:19 ` [PATCH v9 2/9] scsi: ibmvfc: add NOOP command support Tyrel Datwyler
2026-09-11 2:31 ` sashiko-bot
2026-09-11 3:41 ` Tyrel Datwyler
2026-09-11 2:19 ` [PATCH v9 3/9] scsi: ibmvfc: add FPIN extended flag and async sub-CRQ queue handle Tyrel Datwyler
2026-09-11 2:19 ` [PATCH v9 4/9] scsi: ibmvfc: extend async event handlers for async sub-CRQ events Tyrel Datwyler
2026-09-11 2:39 ` sashiko-bot
2026-09-11 3:52 ` Tyrel Datwyler
2026-09-11 2:19 ` [PATCH v9 5/9] scsi: ibmvfc: add interrupt routine for asynchronous sub CRQ Tyrel Datwyler
2026-09-11 2:44 ` sashiko-bot
2026-09-11 3:53 ` Tyrel Datwyler [this message]
2026-09-11 2:19 ` [PATCH v9 6/9] scsi: ibmvfc: extend channel reg/dereg helpers for async sub-CRQ Tyrel Datwyler
2026-09-11 2:19 ` [PATCH v9 7/9] scsi: ibmvfc: fix IRQ leak and guard deregister on channel reg failure Tyrel Datwyler
2026-09-11 2:34 ` sashiko-bot
2026-09-11 2:19 ` [PATCH v9 8/9] scsi: ibmvfc: register and use asynchronous sub CRQ for events Tyrel Datwyler
2026-09-11 2:40 ` sashiko-bot
2026-09-11 2:19 ` [PATCH v9 9/9] scsi: ibmvfc: handle extended FPIN events Tyrel Datwyler
2026-09-11 2:40 ` sashiko-bot
-- strict thread matches above, loose matches on Subject: below --
2026-09-09 19:07 [PATCH v8 0/9] scsi: ibmvfc: make ibmvfc support FPIN messages Dave Marquardt via B4 Relay
2026-09-11 2:08 ` [PATCH v9 5/9] scsi: ibmvfc: add interrupt routine for asynchronous sub CRQ Tyrel Datwyler
2026-09-11 2:31 ` 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=6db82d74-2251-416b-8a29-7caa9301c2c5@linux.ibm.com \
--to=tyreld@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.