Re: INFO: task hung in __blkdev_get

[Dmitry Vyukov]

On Tue, Apr 10, 2018 at 3:04 PM, Tetsuo Handa
<penguin-kernel@xxxxxxxxxxxxxxxxxxx> wrote:
> Dmitry Vyukov wrote:
>> On Tue, Apr 10, 2018 at 12:55 PM, Tetsuo Handa
>> <penguin-kernel@xxxxxxxxxxxxxxxxxxx> wrote:
>> > Hello.
>> >
>> > Since syzbot is reporting so many hung up bug which involves /dev/loopX ,
>> > is it possible to "temporarily" apply below patch for testing under syzbot
>>
>> Unfortunately it's not possible, for full explanation please see:
>> https://github.com/google/syzkaller/blob/master/docs/syzbot.md#no-custom-patches
>>
>
> I mean, sending custom patch to linux.git for -rc and revert the custom patch
> before -final is released. It won't take so much period until we get the result.

Ah, I see, then I guess it wasn't a question to me.


> If syzbot can test arbitrary git tree instead of linux.git, making a branch
> which contains custom patches would be possible.

syzbot tests a set of trees (also net-next and bpf-next at the
moment). But see this reply to Takashi re a similar request:
https://groups.google.com/forum/#!msg/syzkaller-bugs/7ucgCkAJKSk/skZjgavRAQAJ
Note that a syzkaller instances will produce several hundreds of
different crashes within a day, and then a big question is what to do
with them.

What's perfectly possible though is running syzkaller locally, and you
can do it on just any tree you want. I've recently put a script that
setups syzkaller end-to-end with config, compiler and image that
syzbot uses:
https://github.com/google/syzkaller/blob/master/tools/demo_setup.sh
(that uses v4.13, but you can change this to any kernel version).