From: Chris Bainbridge <chris.bainbridge@gmail.com>
To: fengli@smartx.com, hch@lst.de, martin.petersen@oracle.com
Cc: axboe@kernel.dk, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [REGRESSION] critical target error, bisected
Date: Mon, 12 Aug 2024 15:49:04 +0100 [thread overview]
Message-ID: <Zrog4DYXrirhJE7P@debian.local> (raw)
Hello,
Machine is HP Aero 13 laptop. The following error appears in 6.11-rc3
when booted from USB drive:
[ 195.647081] sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[ 195.647093] sd 0:0:0:0: [sda] tag#0 Sense Key : Illegal Request [current]
[ 195.647096] sd 0:0:0:0: [sda] tag#0 Add. Sense: Invalid command operation code
[ 195.647099] sd 0:0:0:0: [sda] tag#0 CDB: Write same(16) 93 08 00 00 00 00 04 dd 42 f8 00 00 2d 48 00 00
[ 195.647101] critical target error, dev sda, sector 81609464 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0
This error appears on two different laptops with different USB drives.
Bisect result:
f874d7210d882cb1c58a8e3da66f61cdc63cd4b4 is the first bad commit
commit f874d7210d882cb1c58a8e3da66f61cdc63cd4b4
Author: Li Feng <fengli@smartx.com>
Date: Thu Jul 18 16:07:22 2024 +0800
scsi: sd: Keep the discard mode stable
There is a scenario where a large number of discard commands are issued
when the iscsi initiator connects to the target and then performs a session
rescan operation. There is a time window, most of the commands are in UNMAP
mode, and some discard commands become WRITE SAME with UNMAP.
The discard mode has been negotiated during the SCSI probe. If the mode is
temporarily changed from UNMAP to WRITE SAME with UNMAP, an I/O ERROR may
occur because the target may not implement WRITE SAME with UNMAP. Keep the
discard mode stable to fix this issue.
Signed-off-by: Li Feng <fengli@smartx.com>
Link: https://lore.kernel.org/r/20240718080751.313102-2-fengli@smartx.com
Reviewed-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
drivers/scsi/sd.c | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
#regzbot introduced: f874d7210d882cb1c58a8e3da66f61cdc63cd4b4
next reply other threads:[~2024-08-12 14:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 14:49 Chris Bainbridge [this message]
2024-08-13 2:09 ` [REGRESSION] critical target error, bisected Martin K. Petersen
2024-08-13 2:21 ` Martin K. Petersen
2024-08-16 3:56 ` Martin K. Petersen
2024-08-16 6:08 ` Chris Bainbridge
2024-08-16 7:59 ` Shinichiro Kawasaki
2024-08-16 8:06 ` hch
2024-08-17 0:51 ` Martin K. Petersen
2024-08-16 8:21 ` John Garry
2024-08-17 0:53 ` [PATCH] scsi: sd: Do not attempt to configure discard unless LBPME is set Martin K. Petersen
2024-08-17 1:28 ` 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=Zrog4DYXrirhJE7P@debian.local \
--to=chris.bainbridge@gmail.com \
--cc=axboe@kernel.dk \
--cc=fengli@smartx.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--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