From: syzbot <syzbot+704bfe2c7d156640ad7a@syzkaller.appspotmail.com>
To: acme@kernel.org, acme@redhat.com,
alexander.shishkin@linux.intel.com, arvid.brodin@alten.se,
ast@kernel.org, bpf@vger.kernel.org, daniel@iogearbox.net,
davem@davemloft.net, jbacik@fb.com, jolsa@redhat.com,
kafai@fb.com, kernel-team@fb.com, linux-kernel@vger.kernel.org,
mingo@kernel.org, mingo@redhat.com, namhyung@kernel.org,
netdev@vger.kernel.org, peterz@infradead.org,
rostedt@goodmis.org, songliubraving@fb.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
torvalds@linux-foundation.org, xiyou.wangcong@gmail.com,
yhs@fb.com
Subject: Re: WARNING in add_event_to_ctx
Date: Thu, 09 Jan 2020 22:50:00 -0800 [thread overview]
Message-ID: <000000000000ddae64059bc388dc@google.com> (raw)
In-Reply-To: <000000000000946842058bc1291d@google.com>
syzbot suspects this bug was fixed by commit:
commit 311633b604063a8a5d3fbc74d0565b42df721f68
Author: Cong Wang <xiyou.wangcong@gmail.com>
Date: Wed Jul 10 06:24:54 2019 +0000
hsr: switch ->dellink() to ->ndo_uninit()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1005033ee00000
start commit: 6fbc7275 Linux 5.2-rc7
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=bff6583efcfaed3f
dashboard link: https://syzkaller.appspot.com/bug?extid=704bfe2c7d156640ad7a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1016165da00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12b27be5a00000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: hsr: switch ->dellink() to ->ndo_uninit()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-01-10 6:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 13:17 WARNING in add_event_to_ctx syzbot
2019-06-20 14:39 ` syzbot
2020-01-10 6:50 ` syzbot [this message]
2020-01-10 14:45 ` Steven Rostedt
2020-01-10 14:48 ` Dmitry Vyukov
2020-01-10 15:01 ` Steven Rostedt
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=000000000000ddae64059bc388dc@google.com \
--to=syzbot+704bfe2c7d156640ad7a@syzkaller.appspotmail.com \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=arvid.brodin@alten.se \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=jbacik@fb.com \
--cc=jolsa@redhat.com \
--cc=kafai@fb.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=songliubraving@fb.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=xiyou.wangcong@gmail.com \
--cc=yhs@fb.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).