public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: JiangJianJun <jiangjianjun3@huawei.com>
To: <James.Bottomley@HansenPartnership.com>,
	<martin.petersen@oracle.com>, <linux-scsi@vger.kernel.org>
Cc: <bvanassche@acm.org>, <john.g.garry@oracle.com>,
	<hewenliang4@huawei.com>, <yangyun50@huawei.com>,
	<wuyifeng10@huawei.com>
Subject: Re: scsi: scsi_debug: make timeout faults by set delay to maximum value
Date: Thu, 13 Nov 2025 19:22:58 +0800	[thread overview]
Message-ID: <20251113112258.367-1-jiangjianjun3@huawei.com> (raw)
In-Reply-To: <7b020e5f-3fca-48eb-bd20-cb0521120f5b@oracle.com>

> The concern which I mentioned before was that we would have competing 
> and potentially conflicting methods to trigger and handle errors.
>
> This specifically is a change from Bart to fix my code. However I added 
> the change to check the abort result.
> 
> I think previously scsi_debug_abort() would just always report success, 
> even if scsi_debug_abort_cmnd() possibly fails, right?
> 
> Now for a fake timeout, there seems to be a problem in 
> scsi_debug_stop_cmnd() that we abort depending on the deferred type, but 
> this is not set for any fake timeout. Or - more specifically - it is not 
> reset for when the scmd is recycled. I think that we should just allow 
> the abort to be successful for that case.

I think your design is rational.

I think the method of simulating timeout is rational because discard-command is
equivalent to the queuecommand executing but returning a success status, which
is clearly not what this interface expects. It is also within expectation that
such an unrational approach might conflict with subsequent changes.

So, I tend to change the discard-command to setting a very much long delay for
schedule.


  reply	other threads:[~2025-11-13 11:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-24 11:55 [PATCH 0/4] scsi_debug improvements John Garry
2025-02-24 11:55 ` [PATCH 1/4] scsi: scsi_debug: Remove sdebug_device_access_info John Garry
2025-02-24 18:04   ` Bart Van Assche
2025-02-24 11:55 ` [PATCH 2/4] scsi: scsi_debug: Remove a reference to in_use_bm John Garry
2025-02-24 11:55 ` [PATCH 3/4] scsi: scsi_debug: Simplify command handling John Garry
2025-02-24 11:55 ` [PATCH 4/4] scsi: scsi_debug: Do not sleep in atomic sections John Garry
2025-11-05 11:57   ` [PATCH] scsi: scsi_debug: make timeout faults by set delay to maximum value JiangJianJun
2025-11-05 12:00   ` JiangJianJun
2025-11-05 12:01   ` JiangJianJun
2025-11-05 11:54     ` John Garry
2025-11-06 12:03       ` JiangJianJun
2025-11-07 10:05         ` John Garry
2025-11-08  8:29           ` JiangJianJun
2025-11-08  9:38             ` John Garry
2025-11-11 10:59               ` JiangJianJun
2025-11-12  8:53                 ` John Garry
2025-11-12 13:38                   ` JiangJianJun
2025-11-12 16:02                     ` John Garry
2025-11-13 11:22                       ` JiangJianJun [this message]
2025-11-13 11:48                         ` John Garry
2025-02-25  1:57 ` [PATCH 0/4] scsi_debug improvements Martin K. Petersen

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=20251113112258.367-1-jiangjianjun3@huawei.com \
    --to=jiangjianjun3@huawei.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=bvanassche@acm.org \
    --cc=hewenliang4@huawei.com \
    --cc=john.g.garry@oracle.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=wuyifeng10@huawei.com \
    --cc=yangyun50@huawei.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