From: syzbot <syzbot+c2d4c3ae3fd90bbaf059@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, ast@kernel.org, davem@davemloft.net,
dhowells@redhat.com, dsahern@gmail.com, dvyukov@google.com,
ebiederm@xmission.com, gs051095@gmail.com, kuznet@ms2.inr.ac.ru,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
oleg@redhat.com, pasha.tatashin@oracle.com, riel@redhat.com,
rppt@linux.vnet.ibm.com, syzkaller-bugs@googlegroups.com,
wangkefeng.wang@huawei.com, weiyongjun1@huawei.com,
yoshfuji@linux-ipv6.org
Subject: Re: WARNING: suspicious RCU usage in pid_task
Date: Sun, 24 Nov 2019 15:05:01 -0800 [thread overview]
Message-ID: <0000000000003c0b2105981fad65@google.com> (raw)
In-Reply-To: <0000000000002b532a056ebcb3eb@google.com>
syzbot has bisected this bug to:
commit 23fb93a4d3f118a900790066d03368a296dce0d6
Author: David Ahern <dsahern@gmail.com>
Date: Wed Apr 18 00:33:23 2018 +0000
net/ipv6: Cleanup exception and cache route handling
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1295147ae00000
start commit: 6f0d349d Merge git://git.kernel.org/pub/scm/linux/kernel/g..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=1195147ae00000
console output: https://syzkaller.appspot.com/x/log.txt?x=1695147ae00000
kernel config: https://syzkaller.appspot.com/x/.config?x=a63be0c83e84d370
dashboard link: https://syzkaller.appspot.com/bug?extid=c2d4c3ae3fd90bbaf059
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14f0a814400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16ce574c400000
Reported-by: syzbot+c2d4c3ae3fd90bbaf059@syzkaller.appspotmail.com
Fixes: 23fb93a4d3f1 ("net/ipv6: Cleanup exception and cache route handling")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-11-24 23:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-16 6:47 WARNING: suspicious RCU usage in pid_task syzbot
2018-06-25 17:45 ` syzbot
2018-09-03 4:56 ` Dmitry Vyukov
2019-11-24 23:05 ` syzbot [this message]
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=0000000000003c0b2105981fad65@google.com \
--to=syzbot+c2d4c3ae3fd90bbaf059@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=ast@kernel.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=dsahern@gmail.com \
--cc=dvyukov@google.com \
--cc=ebiederm@xmission.com \
--cc=gs051095@gmail.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=pasha.tatashin@oracle.com \
--cc=riel@redhat.com \
--cc=rppt@linux.vnet.ibm.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=wangkefeng.wang@huawei.com \
--cc=weiyongjun1@huawei.com \
--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.