From: Douglas Gilbert <dgilbert@interlog.com>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>,
linux-scsi@vger.kernel.org,
"Martin K . Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH 2/2] scsi: scsi_debug: fix sparse lock warnings in sdebug_blk_mq_poll()
Date: Mon, 28 Feb 2022 20:48:46 -0500 [thread overview]
Message-ID: <a0876c6a-3e5e-70ba-e8f0-366ce05a4a67@interlog.com> (raw)
In-Reply-To: <2dda2a2a-dc54-e335-e0eb-574868397277@opensource.wdc.com>
See below:
On 2022-02-28 08:46, Damien Le Moal wrote:
> On 2022/02/28 4:05, Douglas Gilbert wrote:
>> On 2022-02-25 03:45, Damien Le Moal wrote:
>>> The use of the locked boolean variable to control locking and unlocking
>>> of the qc_lock of struct sdebug_queue confuses sparse, leading to a
>>> warning about an unexpected unlock. Simplify the qc_lock lock/unlock
>>> handling code of this function to avoid this warning by removing the
>>> locked boolean variable.
>>
>> See below.
>>
>>>
>>> Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
>>> ---
>>> drivers/scsi/scsi_debug.c | 19 +++++++++----------
>>> 1 file changed, 9 insertions(+), 10 deletions(-)
>>>
>>> diff --git a/drivers/scsi/scsi_debug.c b/drivers/scsi/scsi_debug.c
>>> index f4e97f2224b2..acb32f3e38eb 100644
>>> --- a/drivers/scsi/scsi_debug.c
>>> +++ b/drivers/scsi/scsi_debug.c
>>> @@ -7509,7 +7509,6 @@ static int sdebug_blk_mq_poll(struct Scsi_Host *shost, unsigned int queue_num)
>>> {
>>> bool first;
>>> bool retiring = false;
>>> - bool locked = false;
>>> int num_entries = 0;
>>> unsigned int qc_idx = 0;
>>> unsigned long iflags;
>>> @@ -7525,18 +7524,17 @@ static int sdebug_blk_mq_poll(struct Scsi_Host *shost, unsigned int queue_num)
>>> if (qc_idx >= sdebug_max_queue)
>>> return 0;
>>>
>>> + spin_lock_irqsave(&sqp->qc_lock, iflags);
>>> +
>>> for (first = true; first || qc_idx + 1 < sdebug_max_queue; ) {
>>> - if (!locked) {
>>> - spin_lock_irqsave(&sqp->qc_lock, iflags);
>>> - locked = true;
>>> - }
>>> if (first) {
>>> first = false;
>>> if (!test_bit(qc_idx, sqp->in_use_bm))
>>> continue;
>>> - } else {
>>> - qc_idx = find_next_bit(sqp->in_use_bm, sdebug_max_queue, qc_idx + 1);
>>> }
>>> +
>>> + qc_idx = find_next_bit(sqp->in_use_bm, sdebug_max_queue,
>>> + qc_idx + 1);
>>
>> The original logic is wrong or the above line is wrong. find_next_bit() is not
>> called on the first iteration in the original, but it is with this patch.
>>
>>> if (qc_idx >= sdebug_max_queue)
>>> break;
>>>
>>> @@ -7586,14 +7584,15 @@ static int sdebug_blk_mq_poll(struct Scsi_Host *shost, unsigned int queue_num)
>>> }
>>> WRITE_ONCE(sd_dp->defer_t, SDEB_DEFER_NONE);
>>> spin_unlock_irqrestore(&sqp->qc_lock, iflags);
>>> - locked = false;
>>> scsi_done(scp); /* callback to mid level */
>>> num_entries++;
>>> + spin_lock_irqsave(&sqp->qc_lock, iflags);
>>> if (find_first_bit(sqp->in_use_bm, sdebug_max_queue) >= sdebug_max_queue)
>>> break; /* if no more then exit without retaking spinlock */
>>
>> See that comment on the line above? That is the reason for the guard variable.
>> Defying that comment, the modified code does a superfluous spinlock irqsave
>> and irqrestore.
>
> Rechecking this, there is one point that is bothering me: is it OK to have the
> find_first_bit() outside of the sqp lock ? If not, then this is a bug and the
> extra lock/unlock that my patch add is a fix...
I think you are correct, please fix it.
You will notice that when the spinlock_irq is dropped to call scsi_done(),
that the iteration is restarted.
>>
>> Sparse could be taken as a comment on the amount of grey matter that tool has.
>>
>>
>>> }
>>> - if (locked)
>>> - spin_unlock_irqrestore(&sqp->qc_lock, iflags);
>>> +
>>> + spin_unlock_irqrestore(&sqp->qc_lock, iflags);
>>> +
>>> if (num_entries > 0)
>>> atomic_add(num_entries, &sdeb_mq_poll_count);
>>> return num_entries;
>>
>> Locking issues are extremely difficult to analyze via a unified diff of
>> the function. A copy of the original function is required to make any
>> sense of it.
I was trying to say: it is difficult to understand what diff style output
of a change as shown in a [PATCH] post like this, especially to a function's
locking, will do, without see the __whole__ function.
It is not a criticism of this patchset, but the process in general which loses
important context of the function being patched.
prev parent reply other threads:[~2022-03-01 1:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 8:45 [PATCH 0/2] Fix sparse warnings in scsi_debug Damien Le Moal
2022-02-25 8:45 ` [PATCH 1/2] scsi: scsi_debug: silence sparse unexpected unlock warnings Damien Le Moal
2022-02-28 1:39 ` Douglas Gilbert
2022-02-28 6:58 ` Damien Le Moal
2022-02-28 22:45 ` Douglas Gilbert
2022-02-25 8:45 ` [PATCH 2/2] scsi: scsi_debug: fix sparse lock warnings in sdebug_blk_mq_poll() Damien Le Moal
2022-02-28 2:05 ` Douglas Gilbert
2022-02-28 7:07 ` Damien Le Moal
2022-02-28 13:46 ` Damien Le Moal
2022-03-01 1:48 ` Douglas Gilbert [this message]
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=a0876c6a-3e5e-70ba-e8f0-366ce05a4a67@interlog.com \
--to=dgilbert@interlog.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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