From: syzbot <syzbot+d89b30c46434c433dbf8@syzkaller.appspotmail.com>
To: crecklin@redhat.com, davem@davemloft.net, dvyukov@google.com,
keescook@chromium.org, kuznet@ms2.inr.ac.ru,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-net@vger.kernel.org, netdev@vger.kernel.org,
sbrivio@redhat.com, sd@queasysnail.net,
syzkaller-bugs@googlegroups.com, willy@infradead.org,
yoshfuji@linux-ipv6.org
Subject: Re: WARNING: bad usercopy in corrupted (2)
Date: Tue, 19 Mar 2019 17:49:00 -0700 [thread overview]
Message-ID: <000000000000c7bd5c05847bfcab@google.com> (raw)
In-Reply-To: <000000000000f7cb53057b7ee3cb@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=14a57f83200000
start commit: b8a51b38 fou, fou6: ICMP error handlers for FoU and GUE
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=12a57f83200000
kernel config: https://syzkaller.appspot.com/x/.config?x=c36a72af2123e78a
dashboard link: https://syzkaller.appspot.com/bug?extid=d89b30c46434c433dbf8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=170f6a47400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12e1df7b400000
Reported-by: syzbot+d89b30c46434c433dbf8@syzkaller.appspotmail.com
Fixes: b8a51b38 ("fou, fou6: ICMP error handlers for FoU and GUE")
next prev parent reply other threads:[~2019-03-20 0:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-25 15:30 WARNING: bad usercopy in corrupted (2) syzbot
2018-11-25 21:27 ` Matthew Wilcox
2018-11-25 23:07 ` Matthew Wilcox
2018-11-26 9:01 ` Dmitry Vyukov
2019-03-20 0:49 ` syzbot [this message]
2019-03-20 9:39 ` 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=000000000000c7bd5c05847bfcab@google.com \
--to=syzbot+d89b30c46434c433dbf8@syzkaller.appspotmail.com \
--cc=crecklin@redhat.com \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=keescook@chromium.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-net@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sbrivio@redhat.com \
--cc=sd@queasysnail.net \
--cc=syzkaller-bugs@googlegroups.com \
--cc=willy@infradead.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 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).