[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2825703.dkhYCMB3mh@sven-edge>
Date: Thu, 28 Nov 2019 08:25:34 +0100
From: Sven Eckelmann <sven@...fation.org>
To: syzbot <syzbot+a229d8d995b74f8c4b6c@...kaller.appspotmail.com>
Cc: a@...table.cc, b.a.t.m.a.n@...ts.open-mesh.org,
davem@...emloft.net, jakub.kicinski@...ronome.com,
jhs@...atatu.com, jiri@...nulli.us, linux-kernel@...r.kernel.org,
mareklindner@...mailbox.ch, netdev@...r.kernel.org,
sw@...onwunderlich.de, syzkaller-bugs@...glegroups.com,
vinicius.gomes@...el.com, wang.yi59@....com.cn,
xiyou.wangcong@...il.com
Subject: Re: WARNING in mark_lock (3)
On Thursday, 28 November 2019 03:00:01 CET syzbot wrote:
[...]
> 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=10aee536e00000
Can 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").
Kind regards,
Sven
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists