Linux-Block Archive on lore.kernel.org
 help / Atom feed
* Kernel v5.0-rc1 and blk-mq
@ 2019-01-07 21:21 Bart Van Assche
  2019-01-07 21:30 ` Bart Van Assche
  0 siblings, 1 reply; 2+ messages in thread
From: Bart Van Assche @ 2019-01-07 21:21 UTC (permalink / raw)
  To: Jens Axboe; +Cc: linux-block, Logan Gunthorpe

Hi Jens,

When I tried to run the SRP tests from the blktests repository against the
v5.0 kernel several issues were reported. The same tests pass against kernel
v4.20.

WARNING: CPU: 0 PID: 262 at block/blk-mq.c:683 blk+AF8-mq+AF8-start+AF8-request+-0x234/0x280
Modules linked in: ib+AF8-srp scsi+AF8-transport+AF8-srp target+AF8-core+AF8-pscsi target+AF8-core+AF8-file ib+AF8-srpt target+AF8-core+AF8-iblock target+AF8-core+AF8-mod rdma+AF8-cm iw+AF8-cm ib+AF8-cm scsi+AF8-debug rdma+AF8-rxe ip6+AF8-udp+AF8-tunnel udp+AF8-tunnel null+AF8-blk
dm+AF8-service+AF8-time ib+AF8-umad ib+AF8-uverbs ib+AF8-core mq+AF8-deadline kyber+AF8-iosched bfq scsi+AF8-dh+AF8-rdac scsi+AF8-dh+AF8-emc scsi+AF8-dh
ath crct10dif+AF8-pclmul crc32+AF8-pclmul ghash+AF8-clmulni+AF8-intel aesni+AF8-intel aes+AF8-x86+AF8-64 crypto+AF8-simd cryptd glue+AF8-helper joydev virtio+AF8-console virtio+AF8-balloon serio+AF8-raw qemu+AF8-fw+AF8-cfg iscsi+AF8-tcp libiscsi+AF8-tcp libiscsi
scsi+AF8-transport+AF8-iscsi ip+AF8-tables x+AF8-tables hid+AF8-generic usbhid hid psmouse virtio+AF8-net virtio+AF8-scsi net+AF8-failo
io+AF8-blk failover pata+AF8-acpi i2c+AF8-piix4 +AFs-last unloaded: null+AF8-blk+AF0
+AD0APQA9AD0APQA9AD0APQA9AD0APQA9AD0APQA9AD0APQA9AD0APQA9AD0APQA9AD0APQA9AD0APQA9AD0APQA9AD0APQA9AD0APQA9AD0APQA9AD0APQA9AD0APQA9AD0APQA9AD0APQA9AD0APQA9AD0APQA9AD0APQA9AD0APQA9
sd 4:0:0:0: Power-on or device reset occurred
CPU: 0 PID: 262 Comm: kworker/0:1H Not tainted 5.0.0-rc1-dbg+- +ACM-1
Hardware name: QEMU Standard PC (i440FX +- PIIX, 1996), BIOS 1.10.2-1 04/01/2014
Workqueue: kblockd blk+AF8-mq+AF8-run+AF8-work+AF8-fn
BUG: KASAN: null-ptr-deref in blk+AF8-mq+AF8-dispatch+AF8-rq+AF8-list+-0x116/0xb10
RIP: 0010:blk+AF8-mq+AF8-start+AF8-request+-0x234/0x280
Code: 01 e8 d0 d6 ad ff 85 c0 74 09 80 3d ec 2e b0 01 00 74 2c 65 ff 0d cc c7 97 7e 0f 85 53 fe ff ff e8 bc 11 96 ff e9 49 fe ff ff +ADw-0f+AD4 0b e9 79 fe ff ff 0f 0b e9 2b fe ff ff 0f 0b e9 db fe ff ff e8
Read of size 8 at addr 0000000000000138 by task kworker/2:1H/350
RSP: 0018:ffff88811468fa88 EFLAGS: 00010202
CPU: 2 PID: 350 Comm: kworker/2:1H Not tainted 5.0.0-rc1-dbg+- +ACM-1
RAX: 0000000000000001 RBX: ffff888038c24c00 RCX: ffffffff816a1546
RDX: 0000000000000007 RSI: dffffc0000000000 RDI: ffff888038c24cd4
Hardware name: QEMU Standard PC (i440FX +- PIIX, 1996), BIOS 1.10.2-1 04/01/2014
RBP: ffff88811468faa8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffff88810b1124f0
Workqueue: kblockd blk+AF8-mq+AF8-run+AF8-work+AF8-fn
R13: ffff888038c24cd4 R14: ffff888038c24c1c R15: ffff88803ffe4400
Call Trace:
 dump+AF8-stack+-0x86/0xca
FS:  0000000000000000(0000) GS:ffff88811b600000(0000) knlGS:0000000000000000
 ? blk+AF8-mq+AF8-dispatch+AF8-rq+AF8-list+-0x116/0xb10
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
 kasan+AF8-report.cold.3+-0x5/0x3e
CR2: 0000565114f33710 CR3: 00000001140cc003 CR4: 00000000003606f0
 ? blk+AF8-mq+AF8-dispatch+AF8-rq+AF8-list+-0x116/0xb10
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
 +AF8AXw-asan+AF8-load8+-0x54/0x90
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
 blk+AF8-mq+AF8-dispatch+AF8-rq+AF8-list+-0x116/0xb10
Call Trace:
 scsi+AF8-queue+AF8-rq+-0x9d6/0x1360
 ? blk+AF8-mq+AF8-flush+AF8-busy+AF8-ctxs+-0x172/0x380
 blk+AF8-mq+AF8-dispatch+AF8-rq+AF8-list+-0x5fc/0xb10
 ? blk+AF8-mq+AF8-get+AF8-driver+AF8-tag+-0x270/0x270
 ? blk+AF8-mq+AF8-flush+AF8-busy+AF8-ctxs+-0x172/0x380
 ? mark+AF8-held+AF8-locks+-0xb0/0xb0
 ? blk+AF8-mq+AF8-get+AF8-driver+AF8-tag+-0x270/0x270
 blk+AF8-mq+AF8-sched+AF8-dispatch+AF8-requests+-0x2f7/0x300
 ? mark+AF8-held+AF8-locks+-0xb0/0xb0
 ? blk+AF8-mq+AF8-sched+AF8-restart+-0x40/0x40
 blk+AF8-mq+AF8-sched+AF8-dispatch+AF8-requests+-0x2f7/0x300
 ? rcu+AF8-dynticks+AF8-curr+AF8-cpu+AF8-in+AF8-eqs+-0x4c/0x60
 ? blk+AF8-mq+AF8-sched+AF8-restart+-0x40/0x40
 ? rcu+AF8-is+AF8-watching+-0x10/0x30
 ? rcu+AF8-dynticks+AF8-curr+AF8-cpu+AF8-in+AF8-eqs+-0x4c/0x60
 +AF8AXw-blk+AF8-mq+AF8-run+AF8-hw+AF8-queue+-0xd6/0x180
 ? rcu+AF8-is+AF8-watching+-0x10/0x30
 ? blk+AF8-mq+AF8-end+AF8-request+-0x210/0x210
 +AF8AXw-blk+AF8-mq+AF8-run+AF8-hw+AF8-queue+-0xd6/0x180
 blk+AF8-mq+AF8-run+AF8-work+AF8-fn+-0x27/0x30
 ? blk+AF8-mq+AF8-end+AF8-request+-0x210/0x210
 process+AF8-one+AF8-work+-0x4ae/0xa20
 blk+AF8-mq+AF8-run+AF8-work+AF8-fn+-0x27/0x30
 ? pwq+AF8-dec+AF8-nr+AF8-in+AF8-flight+-0x130/0x130
 process+AF8-one+AF8-work+-0x4ae/0xa20
 worker+AF8-thread+-0x67/0x5b0
 ? pwq+AF8-dec+AF8-nr+AF8-in+AF8-flight+-0x130/0x130
 kthread+-0x1cf/0x1f0
 worker+AF8-thread+-0x67/0x5b0
 ? process+AF8-one+AF8-work+-0xa20/0xa20
 kthread+-0x1cf/0x1f0
 ? kthread+AF8-create+AF8-on+AF8-node+-0xa0/0xa0
 ? process+AF8-one+AF8-work+-0xa20/0xa20
 ret+AF8-from+AF8-fork+-0x24/0x30
 ? kthread+AF8-create+AF8-on+AF8-node+-0xa0/0xa0
+AD0APQA9AD0APQA9AD0APQA9AD0APQA9AD0APQA9AD0APQA9AD0APQA9AD0APQA9AD0APQA9AD0APQA9AD0APQA9AD0APQA9AD0APQA9AD0APQA9AD0APQA9AD0APQA9AD0APQA9AD0APQA9AD0APQA9AD0APQA9AD0APQA9AD0APQA9
 ret+AF8-from+AF8-fork+-0x24/0x30
Disabling lock debugging due to kernel taint
irq event stamp: 3962924
BUG: unable to handle kernel NULL pointer dereference at 0000000000000138
hardirqs last  enabled at (3962923): +AFsAPA-ffffffff811a18d3+AD4AXQ ktime+AF8-get+-0xe3/0x120
hardirqs last disabled at (3962924): +AFsAPA-ffffffff81002859+AD4AXQ trace+AF8-hardirqs+AF8-off+AF8-thunk+-0x1a/0x1c
+ACM-PF error: +AFs-normal kernel read fault+AF0

Bart.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Kernel v5.0-rc1 and blk-mq
  2019-01-07 21:21 Kernel v5.0-rc1 and blk-mq Bart Van Assche
@ 2019-01-07 21:30 ` Bart Van Assche
  0 siblings, 0 replies; 2+ messages in thread
From: Bart Van Assche @ 2019-01-07 21:30 UTC (permalink / raw)
  To: Jens Axboe; +Cc: linux-block, Logan Gunthorpe

On Mon, 2019-01-07 at 13:21 -0800, Bart Van Assche wrote:
+AD4 When I tried to run the SRP tests from the blktests repository against the
+AD4 v5.0 kernel several issues were reported. The same tests pass against kernel
+AD4 v4.20.

A correction: this was triggered by a new test (+ACI-Run sg+AF8-reset while I/O is ongoing+ACI).
Anyway, I don't think that such a test should trigger the following statement in
blk+AF8-mq+AF8-start+AF8-request():

	WARN+AF8-ON+AF8-ONCE(blk+AF8-mq+AF8-rq+AF8-state(rq) +ACEAPQ MQ+AF8-RQ+AF8-IDLE)+ADs

A few kernel versions back I ran sg+AF8-reset manually while I/O was ongoing and that
test passed. So this test result may indicate an issue in the blk-mq request state
rework.

Bart.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, back to index

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-01-07 21:21 Kernel v5.0-rc1 and blk-mq Bart Van Assche
2019-01-07 21:30 ` Bart Van Assche

Linux-Block Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-block/0 linux-block/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-block linux-block/ https://lore.kernel.org/linux-block \
		linux-block@vger.kernel.org linux-block@archiver.kernel.org
	public-inbox-index linux-block


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-block


AGPL code for this site: git clone https://public-inbox.org/ public-inbox