From: syzbot <syzbot+ca740b95a16399ceb9a5@syzkaller.appspotmail.com>
To: davem@davemloft.net, hchunhui@mail.ustc.edu.cn, hdanton@sina.com,
ja@ssi.bg, jmorris@namei.org, kaber@trash.net,
kuznet@ms2.inr.ac.ru, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, yoshfuji@linux-ipv6.org
Subject: Re: WARNING in hrtimer_forward
Date: Sun, 27 Sep 2020 07:29:09 -0700 [thread overview]
Message-ID: <0000000000007d5ec805b04c5fc8@google.com> (raw)
In-Reply-To: <000000000000bd9ee505b01f60e2@google.com>
syzbot has bisected this issue to:
commit 0e7bbcc104baaade4f64205e9706b7d43c46db7d
Author: Julian Anastasov <ja@ssi.bg>
Date: Wed Jul 27 06:56:50 2016 +0000
neigh: allow admin to set NUD_STALE
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1661d187900000
start commit: ba5f4cfe bpf: Add comment to document BTF type PTR_TO_BTF_..
git tree: bpf-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=1561d187900000
console output: https://syzkaller.appspot.com/x/log.txt?x=1161d187900000
kernel config: https://syzkaller.appspot.com/x/.config?x=d44e1360b76d34dc
dashboard link: https://syzkaller.appspot.com/bug?extid=ca740b95a16399ceb9a5
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1148fe4b900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12f5218d900000
Reported-by: syzbot+ca740b95a16399ceb9a5@syzkaller.appspotmail.com
Fixes: 0e7bbcc104ba ("neigh: allow admin to set NUD_STALE")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-09-27 14:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 8:48 WARNING in hrtimer_forward syzbot
2020-09-27 0:38 ` syzbot
2020-09-27 14:29 ` syzbot [this message]
2020-09-28 16:13 ` Thomas Gleixner
[not found] ` <20200928171137.16804-1-hdanton@sina.com>
2020-09-28 18:35 ` Thomas Gleixner
2020-09-30 7:26 ` Dmitry Vyukov
[not found] ` <20200927080452.18340-1-hdanton@sina.com>
2020-09-28 14:18 ` Thomas Gleixner
2021-11-03 9:21 ` [syzbot] " syzbot
2021-12-04 10:19 ` Dmitry Vyukov
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=0000000000007d5ec805b04c5fc8@google.com \
--to=syzbot+ca740b95a16399ceb9a5@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=hchunhui@mail.ustc.edu.cn \
--cc=hdanton@sina.com \
--cc=ja@ssi.bg \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=yoshfuji@linux-ipv6.org \
/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).