From: syzbot <syzbot+20fddccabc274e99398e@syzkaller.appspotmail.com>
To: andy.shevchenko@gmail.com, bp@alien8.de, davem@davemloft.net,
douly.fnst@cn.fujitsu.com, hpa@zytor.com, konrad.wilk@oracle.com,
kuznet@ms2.inr.ac.ru, len.brown@intel.com,
linux-kernel@vger.kernel.org, mingo@redhat.com,
netdev@vger.kernel.org, puwen@hygon.cn, rppt@linux.vnet.ibm.com,
sbrivio@redhat.com, sd@queasysnail.net,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
ville.syrjala@linux.intel.com, x86@kernel.org,
yoshfuji@linux-ipv6.org
Subject: Re: WARNING in update_load_avg
Date: Wed, 20 Mar 2019 05:55:00 -0700 [thread overview]
Message-ID: <0000000000002fbe8d0584862154@google.com> (raw)
In-Reply-To: <0000000000009ce9ee057b0be7f8@google.com>
syzbot has bisected this bug to:
commit b8a51b38e4d4dec3e379d52c0fe1a66827f7cf1e
Author: Stefano Brivio <sbrivio@redhat.com>
Date: Thu Nov 8 11:19:23 2018 +0000
fou, fou6: ICMP error handlers for FoU and GUE
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14a48993200000
start commit: b8a51b38 fou, fou6: ICMP error handlers for FoU and GUE
git tree: net-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=16a48993200000
console output: https://syzkaller.appspot.com/x/log.txt?x=12a48993200000
kernel config: https://syzkaller.appspot.com/x/.config?x=d86f24333880b605
dashboard link: https://syzkaller.appspot.com/bug?extid=20fddccabc274e99398e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10272c5d400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=157bd093400000
Reported-by: syzbot+20fddccabc274e99398e@syzkaller.appspotmail.com
Fixes: b8a51b38 ("fou, fou6: ICMP error handlers for FoU and GUE")
next prev parent reply other threads:[~2019-03-20 12:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 22:19 WARNING in update_load_avg syzbot
2019-03-20 12:55 ` syzbot [this message]
2019-03-20 13:01 ` 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=0000000000002fbe8d0584862154@google.com \
--to=syzbot+20fddccabc274e99398e@syzkaller.appspotmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=bp@alien8.de \
--cc=davem@davemloft.net \
--cc=douly.fnst@cn.fujitsu.com \
--cc=hpa@zytor.com \
--cc=konrad.wilk@oracle.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=puwen@hygon.cn \
--cc=rppt@linux.vnet.ibm.com \
--cc=sbrivio@redhat.com \
--cc=sd@queasysnail.net \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=ville.syrjala@linux.intel.com \
--cc=x86@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.