On 1/10/19 6:09 PM, Douglas Gilbert wrote:
On 2019-01-10 6:22 p.m., Bart Van Assche wrote:
Hi Doug,
Have you ever tried to run the libiscsi conformance tests against
the scsi_debug driver? I tried the following:
modprobe scsi_debug delay=0 max_luns=3
dev=$(for f in
/sys/bus/pseudo/drivers/scsi_debug/adapter*/host*/target*/[0-9]*/block/*;
do echo $f; break; done)
dev=/dev/$(basename $dev)
libiscsi/test-tool/iscsi-test-cu --dataloss --allow-sanitize "$dev"
That test triggers the following output:
BUG: unable to handle kernel paging request at ffffa8d741235e00
PGD 13b141067 P4D 13b141067 PUD 13b146067 PMD 6fc5a067 PTE 0
Oops: 0002 [#1] SMP PTI
CPU: 3 PID: 4967 Comm: iscsi-test-cu Not tainted 4.18.0-13-generic
#14-Ubuntu
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1
04/01/2014
RIP: 0010:memcpy_erms+0x6/0x10
Code: ff ff ff 90 eb 1e 0f 1f 00 48 89 f8 48 89 d1 48 c1 e9 03 83 e2
07 f3 48 a5 89 d1 f3 a4 c3 66 0f 1f 44 00 00 48 89 f8 48 89 d1 <f3> a4
c3 0f 1f 80 00 00 00 00 48 89 f8 48 83 fa 20 72 7e 40 38 fe
Call Trace:
sg_copy_to_buffer+0x12/0x20
fetch_to_dev_buffer+0x4a/0x60 [scsi_debug]
resp_write_same.part.35+0x125/0x190 [scsi_debug]
It would be useful to know what the WRITE SAME(16) cdb was.
I'm not sure setting opts=1 (via /sys/bus/pseudo/drivers/scsi_debug
for example) will provide more useful information unless a prior
command emulation is causing corruption.
Hi Doug,
Are you aware that libiscsi is open source and that you can easily run
that testsuite yourself?
Thanks,
Bart.
