* Re: WARNING in mark_lock (3) [not found] <00000000000038b5c205983c2df4@google.com> @ 2019-11-28 2:00 ` syzbot 2019-11-28 7:25 ` Sven Eckelmann 0 siblings, 1 reply; 6+ messages in thread From: syzbot @ 2019-11-28 2:00 UTC (permalink / raw) To: a, b.a.t.m.a.n, davem, jakub.kicinski, jhs, jiri, linux-kernel, mareklindner, netdev, sven, sw, syzkaller-bugs, vinicius.gomes, wang.yi59, xiyou.wangcong syzbot has bisected this bug to: commit d665c1281bc89ac85b8b0c058c22a3f94640a1d6 Author: Yi Wang <wang.yi59@zte.com.cn> Date: Mon Oct 21 23:57:42 2019 +0000 net: sched: taprio: fix -Wmissing-prototypes warnings 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 console output: https://syzkaller.appspot.com/x/log.txt?x=172ee536e00000 kernel config: https://syzkaller.appspot.com/x/.config?x=595c15c951695d1b dashboard link: https://syzkaller.appspot.com/bug?extid=a229d8d995b74f8c4b6c syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1511af5ee00000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16e0f17ae00000 Reported-by: syzbot+a229d8d995b74f8c4b6c@syzkaller.appspotmail.com Fixes: d665c1281bc8 ("net: sched: taprio: fix -Wmissing-prototypes warnings") For information about bisection process see: https://goo.gl/tpsmEJ#bisection ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: WARNING in mark_lock (3) 2019-11-28 2:00 ` WARNING in mark_lock (3) syzbot @ 2019-11-28 7:25 ` Sven Eckelmann 2019-11-28 8:40 ` Dmitry Vyukov 0 siblings, 1 reply; 6+ messages in thread From: Sven Eckelmann @ 2019-11-28 7:25 UTC (permalink / raw) To: syzbot Cc: a, b.a.t.m.a.n, davem, jakub.kicinski, jhs, jiri, linux-kernel, mareklindner, netdev, sw, syzkaller-bugs, vinicius.gomes, wang.yi59, xiyou.wangcong [-- Attachment #1: Type: text/plain, Size: 576 bytes --] 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 [-- Attachment #2: This is a digitally signed message part. --] [-- Type: application/pgp-signature, Size: 833 bytes --] ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: WARNING in mark_lock (3) 2019-11-28 7:25 ` Sven Eckelmann @ 2019-11-28 8:40 ` Dmitry Vyukov 2019-11-28 8:46 ` Sven Eckelmann 0 siblings, 1 reply; 6+ messages in thread From: Dmitry Vyukov @ 2019-11-28 8:40 UTC (permalink / raw) To: Sven Eckelmann, syzkaller Cc: syzbot, a, b.a.t.m.a.n, David Miller, Jakub Kicinski, Jamal Hadi Salim, Jiří Pírko, LKML, mareklindner, netdev, sw, syzkaller-bugs, vinicius.gomes, wang.yi59, Cong Wang On Thu, Nov 28, 2019 at 8:25 AM Sven Eckelmann <sven@narfation.org> wrote: > > 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"). +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... ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: WARNING in mark_lock (3) 2019-11-28 8:40 ` Dmitry Vyukov @ 2019-11-28 8:46 ` Sven Eckelmann 2019-11-28 8:54 ` Dmitry Vyukov 0 siblings, 1 reply; 6+ messages in thread From: Sven Eckelmann @ 2019-11-28 8:46 UTC (permalink / raw) To: Dmitry Vyukov Cc: syzkaller, syzbot, a, b.a.t.m.a.n, David Miller, Jakub Kicinski, Jamal Hadi Salim, Jiří Pírko, LKML, mareklindner, netdev, sw, syzkaller-bugs, vinicius.gomes, wang.yi59, Cong Wang [-- Attachment #1: Type: text/plain, Size: 1409 bytes --] On Thursday, 28 November 2019 09:40:32 CET Dmitry Vyukov wrote: > On Thu, Nov 28, 2019 at 8:25 AM Sven Eckelmann <sven@narfation.org> wrote: > > > > 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"). > > +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... I was thinking more about rerunning the same bisect but tell it to assume "crashed: general protection fault in batadv_iv_ogm_queue_add" as OK instead of assuming that it is a crashed like the previous "crashed: WARNING in mark_lock". Just to get a non-bogus bisect result. Or try to rerun the bisect between 40e220b4218b and 89d57dddd7d319ded00415790a0bb3c954b7e386 Kind regards, Sven [-- Attachment #2: This is a digitally signed message part. --] [-- Type: application/pgp-signature, Size: 833 bytes --] ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: WARNING in mark_lock (3) 2019-11-28 8:46 ` Sven Eckelmann @ 2019-11-28 8:54 ` Dmitry Vyukov 2019-11-28 9:03 ` Sven Eckelmann 0 siblings, 1 reply; 6+ messages in thread From: Dmitry Vyukov @ 2019-11-28 8:54 UTC (permalink / raw) To: Sven Eckelmann Cc: syzkaller, syzbot, a, b.a.t.m.a.n, David Miller, Jakub Kicinski, Jamal Hadi Salim, Jiří Pírko, LKML, mareklindner, netdev, sw, syzkaller-bugs, vinicius.gomes, wang.yi59, Cong Wang On Thu, Nov 28, 2019 at 9:46 AM Sven Eckelmann <sven@narfation.org> wrote: > > On Thursday, 28 November 2019 09:40:32 CET Dmitry Vyukov wrote: > > On Thu, Nov 28, 2019 at 8:25 AM Sven Eckelmann <sven@narfation.org> wrote: > > > > > > 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"). > > > > +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... > > I was thinking more about rerunning the same bisect but tell it to assume > "crashed: general protection fault in batadv_iv_ogm_queue_add" as OK instead > of assuming that it is a crashed like the previous "crashed: WARNING in > mark_lock". Just to get a non-bogus bisect result. Or try to rerun the > bisect between 40e220b4218b and 89d57dddd7d319ded00415790a0bb3c954b7e386 But... but this done by a program. What do you mean by "tell it"? ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: WARNING in mark_lock (3) 2019-11-28 8:54 ` Dmitry Vyukov @ 2019-11-28 9:03 ` Sven Eckelmann 0 siblings, 0 replies; 6+ messages in thread From: Sven Eckelmann @ 2019-11-28 9:03 UTC (permalink / raw) To: Dmitry Vyukov Cc: syzkaller, syzbot, a, b.a.t.m.a.n, David Miller, Jakub Kicinski, Jamal Hadi Salim, Jiří Pírko, LKML, mareklindner, netdev, sw, syzkaller-bugs, vinicius.gomes, wang.yi59, Cong Wang [-- Attachment #1: Type: text/plain, Size: 663 bytes --] On Thursday, 28 November 2019 09:54:15 CET Dmitry Vyukov wrote: [...] > > I was thinking more about rerunning the same bisect but tell it to assume > > "crashed: general protection fault in batadv_iv_ogm_queue_add" as OK instead > > of assuming that it is a crashed like the previous "crashed: WARNING in > > mark_lock". Just to get a non-bogus bisect result. Or try to rerun the > > bisect between 40e220b4218b and 89d57dddd7d319ded00415790a0bb3c954b7e386 > > But... but this done by a program. What do you mean by "tell it"? Sorry that I asked about what the infrastructure around syzbot can do and how the interaction with it looks like. Kind regards, Sven [-- Attachment #2: This is a digitally signed message part. --] [-- Type: application/pgp-signature, Size: 833 bytes --] ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2019-11-28 9:03 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <00000000000038b5c205983c2df4@google.com>
2019-11-28 2:00 ` WARNING in mark_lock (3) syzbot
2019-11-28 7:25 ` Sven Eckelmann
2019-11-28 8:40 ` Dmitry Vyukov
2019-11-28 8:46 ` Sven Eckelmann
2019-11-28 8:54 ` Dmitry Vyukov
2019-11-28 9:03 ` Sven Eckelmann
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox