From: Bart Van Assche <bvanassche@acm.org>
To: Chaohai Chen <wdhh6@aliyun.com>,
James.Bottomley@HansenPartnership.com,
martin.petersen@oracle.com
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scsi: core: Fix missing lock when read async_scan in Scsi_Host
Date: Mon, 2 Mar 2026 06:37:12 -0800 [thread overview]
Message-ID: <5ddfed76-1871-480a-ab28-a0462055e417@acm.org> (raw)
In-Reply-To: <20260302121343.1630837-1-wdhh6@aliyun.com>
On 3/2/26 4:13 AM, Chaohai Chen wrote:
> +static bool scsi_test_async_scan(struct Scsi_Host *shost)
> +{
> + bool async;
> + unsigned long flags;
> +
> + lockdep_assert_not_held(shost->host_lock);
> +
> + spin_lock_irqsave(shost->host_lock, flags);
> + async = shost->async_scan;
> + spin_unlock_irqrestore(shost->host_lock, flags);
> +
> + return async;
> +}
Please use scoped_guard(), e.g. as follows:
static bool scsi_scan_async(struct Scsi_Host *shost)
{
scoped_guard(spinlock_irqsave, shost->host_lock)
return shost->async_scan;
}
> +static void scsi_set_async_scan(struct Scsi_Host *shost)
> +{
> + unsigned long flags;
> +
> + lockdep_assert_not_held(shost->host_lock);
> +
> + spin_lock_irqsave(shost->host_lock, flags);
> + shost->async_scan = 1;
> + spin_unlock_irqrestore(shost->host_lock, flags);
> +}
> +
> +static void scsi_clear_async_scan(struct Scsi_Host *shost)
> +{
> + unsigned long flags;
> +
> + lockdep_assert_not_held(shost->host_lock);
> +
> + spin_lock_irqsave(shost->host_lock, flags);
> + shost->async_scan = 0;
> + spin_unlock_irqrestore(shost->host_lock, flags);
> +}
Please drop the scsi_set_async_scan() and scsi_clear_async_scan()
functions since these only have one caller.
Thanks,
Bart.
next prev parent reply other threads:[~2026-03-02 14:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 12:13 [PATCH] scsi: core: Fix missing lock when read async_scan in Scsi_Host Chaohai Chen
2026-03-02 14:37 ` Bart Van Assche [this message]
2026-03-03 8:45 ` Damien Le Moal
2026-03-03 9:20 ` Chaohai Chen
2026-03-03 9:28 ` Damien Le Moal
2026-03-03 15:12 ` Christoph Hellwig
2026-03-03 16:25 ` James Bottomley
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=5ddfed76-1871-480a-ab28-a0462055e417@acm.org \
--to=bvanassche@acm.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=wdhh6@aliyun.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