Kernel v5.0, scsi_debug and libiscsi

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Doug,

Have you ever tried to run the libiscsi conformance tests against
the scsi+AF8-debug driver? I tried the following:

modprobe scsi+AF8-debug delay+AD0-0 max+AF8-luns+AD0-3
dev+AD0AJA(for f in /sys/bus/pseudo/drivers/scsi+AF8-debug/adapter+ACo-/host+ACo-/target+ACo-/+AFs-0-9+AF0AKg-/block/+ACoAOw do echo +ACQ-f+ADs break+ADs done)
dev+AD0-/dev/+ACQ(basename +ACQ-dev)
libiscsi/test-tool/iscsi-test-cu --dataloss --allow-sanitize +ACIAJA-dev+ACI

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 +AFsAIw-1+AF0 SMP PTI
CPU: 3 PID: 4967 Comm: iscsi-test-cu Not tainted 4.18.0-13-generic +ACM-14-Ubuntu
Hardware name: QEMU Standard PC (i440FX +- PIIX, 1996), BIOS 1.10.2-1 04/01/2014
RIP: 0010:memcpy+AF8-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 +ADw-f3+AD4 a4 c3 0f 1f 80 00 00 00 00 48 89 f8 48 83 fa 20 72 7e 40 38 fe 
Call Trace:
 sg+AF8-copy+AF8-to+AF8-buffer+-0x12/0x20
 fetch+AF8-to+AF8-dev+AF8-buffer+-0x4a/0x60 +AFs-scsi+AF8-debug+AF0
 resp+AF8-write+AF8-same.part.35+-0x125/0x190 +AFs-scsi+AF8-debug+AF0
 resp+AF8-write+AF8-same+AF8-16+-0x84/0xe0 +AFs-scsi+AF8-debug+AF0
 schedule+AF8-resp+-0x4b/0x790 +AFs-scsi+AF8-debug+AF0
 scsi+AF8-debug+AF8-queuecommand+-0x218/0x9c0 +AFs-scsi+AF8-debug+AF0
 scsi+AF8-dispatch+AF8-cmd+-0x98/0x230
 scsi+AF8-queue+AF8-rq+-0x4dc/0x5b0
 blk+AF8-mq+AF8-dispatch+AF8-rq+AF8-list+-0x93/0x4f0
 blk+AF8-mq+AF8-do+AF8-dispatch+AF8-ctx+-0xcd/0x130
 blk+AF8-mq+AF8-sched+AF8-dispatch+AF8-requests+-0x156/0x190
 +AF8AXw-blk+AF8-mq+AF8-run+AF8-hw+AF8-queue+-0x57/0xe0
 +AF8AXw-blk+AF8-mq+AF8-delay+AF8-run+AF8-hw+AF8-queue+-0x14d/0x160
 blk+AF8-mq+AF8-run+AF8-hw+AF8-queue+-0x5a/0x120
 blk+AF8-mq+AF8-sched+AF8-insert+AF8-request+-0x11d/0x180
 blk+AF8-execute+AF8-rq+AF8-nowait+-0x6f/0x100
 blk+AF8-execute+AF8-rq+-0x50/0xb0
 sg+AF8-io+-0x199/0x410
 scsi+AF8-cmd+AF8-ioctl+-0x1b9/0x3f0
 scsi+AF8-cmd+AF8-blk+AF8-ioctl+-0x51/0x61
 sd+AF8-ioctl+-0xcd/0x1c0
 blkdev+AF8-ioctl+-0x3b8/0x980
 block+AF8-ioctl+-0x3d/0x50
 do+AF8-vfs+AF8-ioctl+-0xa8/0x620
 ksys+AF8-ioctl+-0x67/0x90
 +AF8AXw-x64+AF8-sys+AF8-ioctl+-0x1a/0x20
 do+AF8-syscall+AF8-64+-0x5a/0x110
 entry+AF8-SYSCALL+AF8-64+AF8-after+AF8-hwframe+-0x44/0xa9

Is this reproducible on your test setup?

Thanks,

Bart.




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]

  Powered by Linux