From: syzbot <syzbot+a229d8d995b74f8c4b6c@syzkaller•appspotmail.com>
To: a@unstable•cc, b.a.t.m.a.n@lists•open-mesh.org,
davem@davemloft•net, jakub.kicinski@netronome•com,
jhs@mojatatu•com, jiri@resnulli•us, linux-kernel@vger•kernel.org,
mareklindner@neomailbox•ch, netdev@vger•kernel.org,
sven@narfation•org, sw@simonwunderlich•de,
syzkaller-bugs@googlegroups•com, vinicius.gomes@intel•com,
wang.yi59@zte•com.cn, xiyou.wangcong@gmail•com
Subject: Re: WARNING in mark_lock (3)
Date: Wed, 27 Nov 2019 18:00:01 -0800 [thread overview]
Message-ID: <0000000000009aa32205985e78b6@google.com> (raw)
In-Reply-To: <00000000000038b5c205983c2df4@google.com>
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
next prev parent reply other threads:[~2019-11-28 2:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 9:05 WARNING in mark_lock (3) syzbot
2019-11-27 19:30 ` syzbot
2019-11-28 2:00 ` syzbot [this message]
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0000000000009aa32205985e78b6@google.com \
--to=syzbot+a229d8d995b74f8c4b6c@syzkaller$(echo .)appspotmail.com \
--cc=a@unstable$(echo .)cc \
--cc=b.a.t.m.a.n@lists$(echo .)open-mesh.org \
--cc=davem@davemloft$(echo .)net \
--cc=jakub.kicinski@netronome$(echo .)com \
--cc=jhs@mojatatu$(echo .)com \
--cc=jiri@resnulli$(echo .)us \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=mareklindner@neomailbox$(echo .)ch \
--cc=netdev@vger$(echo .)kernel.org \
--cc=sven@narfation$(echo .)org \
--cc=sw@simonwunderlich$(echo .)de \
--cc=syzkaller-bugs@googlegroups$(echo .)com \
--cc=vinicius.gomes@intel$(echo .)com \
--cc=wang.yi59@zte$(echo .)com.cn \
--cc=xiyou.wangcong@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox