[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201804102204.BDF48937.LMHJVFOFFOOSQt@I-love.SAKURA.ne.jp>
Date: Tue, 10 Apr 2018 22:04:36 +0900
From: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
To: dvyukov@...gle.com, axboe@...nel.dk
Cc: tom.leiming@...il.com, mingo@...hat.com, peterz@...radead.org,
bot+48594378e9851eab70bcd6f99327c7db58c5a28a@...kaller.appspotmail.com,
linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com,
osandov@...com
Subject: Re: INFO: task hung in __blkdev_get
Dmitry Vyukov wrote:
> On Tue, Apr 10, 2018 at 12:55 PM, Tetsuo Handa
> <penguin-kernel@...ove.sakura.ne.jp> 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.
If syzbot can test arbitrary git tree instead of linux.git, making a branch
which contains custom patches would be possible.
>
> > ( after "block/loop: fix deadlock after loop_set_status" and
> > "loop: fix LOOP_GET_STATUS lock imbalance" in linux-block.git#for-linus
> > are merged into linux.git )?
Powered by blists - more mailing lists