linux-kernel - Re: [BUG] kernel BUG at /.../block/cfq-iosched.c:3145!

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <53454CBC.9060905@fb.com>
Date:	Wed, 9 Apr 2014 07:35:56 -0600
From:	Jens Axboe <axboe@...com>
To:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
CC:	Jan Kara <jack@...e.cz>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	James Bottomley <James.Bottomley@...senPartnership.com>,
	Brian J King <bjking1@...ibm.com>
Subject: Re: [BUG] kernel BUG at /.../block/cfq-iosched.c:3145!

On 04/08/2014 10:44 PM, Benjamin Herrenschmidt wrote:
> Hi folks !
>
> While testing a branch of fixes before I send it to Linus, which
> happens to be based on 18a1a7a1d862ae0794a0179473d08a414dd49234,
> I hit this:
>
> kernel BUG at /home/benh/linux-powerpc-test/block/cfq-iosched.c:3145!
> cpu 0x3c: Vector: 700 (Program Check) at [c000003ca69bb190]
>      pc: c00000000033b05c: .cfq_dispatch_requests+0x90/0x99c
>      lr: c00000000033b038: .cfq_dispatch_requests+0x6c/0x99c
>      sp: c000003ca69bb410
>     msr: 9000000000029032
>    current = 0xc000003ca63d32a0
>    paca    = 0xc00000000ffef000	 softe: 0	 irq_happened: 0x01
>      pid   = 3487, comm = smartd
> kernel BUG at /home/benh/linux-powerpc-test/block/cfq-iosched.c:3145!
> enter ? for help
> [c000003ca69bb4c0] c00000000032000c .elv_drain_elevator+0x70/0xc8
> [c000003ca69bb540] c000000000320140 .__elv_add_request+0xdc/0x27c
> [c000003ca69bb5e0] c0000000003286f8 .blk_execute_rq_nowait+0xc0/0xf8
> [c000003ca69bb670] c0000000003287ec .blk_execute_rq+0xbc/0xe8
> [c000003ca69bb810] c000000000332350 .sg_io+0x218/0x39c
> [c000003ca69bb930] c000000000332c3c .scsi_cmd_ioctl+0x270/0x4ac
> [c000003ca69bba70] c0000000005d559c .sd_ioctl+0xa4/0xd8
> [c000003ca69bbb20] c00000000032eb1c .__blkdev_driver_ioctl+0x34/0x54
> [c000003ca69bbb90] c00000000032f83c .blkdev_ioctl+0x7b8/0x850
> [c000003ca69bbc40] c00000000018d6e0 .block_ioctl+0x4c/0x60
> [c000003ca69bbcb0] c0000000001691cc .do_vfs_ioctl+0x5cc/0x670
> [c000003ca69bbd90] c0000000001692b4 .SyS_ioctl+0x44/0x70
> [c000003ca69bbe30] c00000000000a024 syscall_exit+0x0/0x98
> --- Exception: c00 (System Call) at 00003fffb5240ee0
>
> The storage driver is our usual IBM "IPR".
>
> Is that a known issue ?

Nope, that's not a known issue. This must be related to the FIFO 
changes... How reproducible is this?

-- 
Jens Axboe

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/