From: John Garry <john.g.garry@oracle.com>
To: Yi Zhang <yi.zhang@redhat.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-block <linux-block@vger.kernel.org>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>
Subject: Re: [regression][bisected] blktests scsi/004 failed
Date: Tue, 28 Mar 2023 08:00:33 +0100 [thread overview]
Message-ID: <c359daa5-e282-bb82-7ef4-a3826e06675c@oracle.com> (raw)
In-Reply-To: <CAHj4cs_RuqDeoZhbqZgMTx1oQBN+mwFgTpuwE4h0PV0LHYQCpw@mail.gmail.com>
On 28/03/2023 03:53, Yi Zhang wrote:
> Hello
>
> I found blktests scsi/004 failed[2] on the latest linux-scsi/for-next,
> bisecting shows it was introduced from[1], pls help check it and let
> me know if you need any testing for it, thanks.
Thanks for the report. I have sent a fix in
https://lore.kernel.org/linux-scsi/20230327074310.1862889-1-john.g.garry@oracle.com/T/#ma8b4e8856df99139ae4879fa0f49befbf69f1a57
Please check it.
>
> [1]
> 151f0ec9ddb5 (HEAD) scsi: scsi_debug: Drop sdebug_dev_info.num_in_q
> [2]
> + ./check scsi/004
> scsi/004 (ensure repeated TASK SET FULL results in EIO on timing out
> command) [failed]
> runtime 1.889s ... 1.851s
> --- tests/scsi/004.out 2023-03-27 02:51:16.755636763 -0400
> +++ /root/blktests/results/nodev/scsi/004.out.bad 2023-03-27
> 22:49:53.511526901 -0400
> @@ -1,3 +1,2 @@
> Running scsi/004
> -Input/output error
> Test complete
> dmesg:
> [ 268.314709] run blktests scsi/004 at 2023-03-27 22:49:51
> [ 268.325391] scsi_debug:sdebug_driver_probe: scsi_debug: trim
> poll_queues to 0. poll_q/nr_hw = (0/1)
> [ 268.325398] scsi host0: scsi_debug: version 0191 [20210520]
> dev_size_mb=8, opts=0x0, submit_queues=1, statistics=1
> [ 268.325575] scsi 0:0:0:0: Direct-Access Linux scsi_debug
> 0191 PQ: 0 ANSI: 7
> [ 268.325693] sd 0:0:0:0: Attached scsi generic sg0 type 0
> [ 268.325775] sd 0:0:0:0: Power-on or device reset occurred
> [ 268.345884] sd 0:0:0:0: [sda] 16384 512-byte logical blocks: (8.39
> MB/8.00 MiB)
> [ 268.355905] sd 0:0:0:0: [sda] Write Protect is off
> [ 268.355909] sd 0:0:0:0: [sda] Mode Sense: 73 00 10 08
> [ 268.375943] sd 0:0:0:0: [sda] Write cache: enabled, read cache:
> enabled, supports DPO and FUA
> [ 268.406011] sd 0:0:0:0: [sda] Preferred minimum I/O size 512 bytes
> [ 268.406016] sd 0:0:0:0: [sda] Optimal transfer size 524288 bytes
> [ 268.537442] sd 0:0:0:0: [sda] Attached SCSI disk
> [ 270.067115] sd 0:0:0:0: [sda] Synchronizing SCSI cache
>
>
next prev parent reply other threads:[~2023-03-28 7:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 2:53 [regression][bisected] blktests scsi/004 failed Yi Zhang
2023-03-28 7:00 ` John Garry [this message]
2023-03-28 7:29 ` Yi Zhang
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=c359daa5-e282-bb82-7ef4-a3826e06675c@oracle.com \
--to=john.g.garry@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=yi.zhang@redhat.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;
as well as URLs for NNTP newsgroup(s).