Re: WARNING in mark_lock (3)
From: Dmitry Vyukov <dvyukov@google.com>
Date: 2019-11-28 08:40:46
Also in:
batman, lkml
From: Dmitry Vyukov <dvyukov@google.com>
Date: 2019-11-28 08:40:46
Also in:
batman, lkml
On Thu, Nov 28, 2019 at 8:25 AM Sven Eckelmann [off-list ref] wrote:
On Thursday, 28 November 2019 03:00:01 CET syzbot wrote: [...]quoted
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=132ee536e00000 start commit: 89d57ddd Merge tag 'media/v5.5-1' of git://git.kernel.org/.. git tree: upstream final crash: https://syzkaller.appspot.com/x/report.txt?x=10aee536e00000Can the syzbot infrastructure be told to ignore this crash in the bisect run? Because this should be an unrelated crash which is (hopefully) fixed in 40e220b4218b ("batman-adv: Avoid free/alloc race when handling OGM buffer").
+syzkaller mailing list for syzbot discussion Hi Sven, There is no such functionality at the moment. What exactly do you mean? Somehow telling it interactively? Or hardcode some set of crashes for linux? I don't see how any of these options can really work...