linux-kernel - Re: block: hung task writing to device

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20170711000320.qnrhawjzdrbhjyzk@sasha-lappy>
Date:   Tue, 11 Jul 2017 00:02:34 +0000
From:   "Levin, Alexander (Sasha Levin)" <alexander.levin@...izon.com>
To:     Jens Axboe <axboe@...nel.dk>
CC:     "linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: block: hung task writing to device

On Sat, Jul 08, 2017 at 07:29:20PM -0600, Jens Axboe wrote:
>On 07/08/2017 01:06 PM, Levin, Alexander (Sasha Levin) wrote:
>> Hi all,
>>
>> syzkaller seems to be hitting a lockup with the reproducer below:
>
>Thanks for the reproducer, but this is missing a lot of detail that we
>need to debug this issue. Is this a regression since 4.12? What storage
>device is this? Is the device using an IO scheduler?

I've started seeing this while testing on -next, so this regression started after v4.12.

The fuzzer runs in qemu, the block device is the result of the "-hda" parameter to qemu. As far as I can tell this results the creation of an ATA device.

>dmesg after boot and .config would be helpful, too.

Attached boot dmesg and config.

-- 

Thanks,
Sasha

Download attachment "bootlog.txt.gz" of type "application/gzip" (17138 bytes)

Download attachment "config-sasha.gz" of type "application/gzip" (32846 bytes)