From: syzbot <syzbot+59752237f7ab21c3f3c3@syzkaller.appspotmail.com>
To: davem@davemloft.net, eric.dumazet@gmail.com, fw@strlen.de,
herbert@gondor.apana.org.au, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, steffen.klassert@secunet.com,
suyj.fnst@cn.fujitsu.com, syzkaller-bugs@googlegroups.com
Subject: Re: WARNING: suspicious RCU usage in xfrm_alloc_userspi
Date: Tue, 19 Mar 2019 13:59:00 -0700 [thread overview]
Message-ID: <0000000000003ff5a5058478c6c4@google.com> (raw)
In-Reply-To: <0000000000007783a2058474a0b9@google.com>
syzbot has bisected this bug to:
commit f10e0010fae8174dc20bdc872bcaa85baa925cb7
Author: Su Yanjun <suyj.fnst@cn.fujitsu.com>
Date: Thu Mar 7 01:54:08 2019 +0000
net: xfrm: Add '_rcu' tag for rcu protected pointer in netns_xfrm
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1644ec8b200000
start commit: f10e0010 net: xfrm: Add '_rcu' tag for rcu protected point..
git tree: linux-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=1544ec8b200000
console output: https://syzkaller.appspot.com/x/log.txt?x=1144ec8b200000
kernel config: https://syzkaller.appspot.com/x/.config?x=59cd5d43b5df6955
dashboard link: https://syzkaller.appspot.com/bug?extid=59752237f7ab21c3f3c3
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14e70cb3200000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17292127200000
Reported-by: syzbot+59752237f7ab21c3f3c3@syzkaller.appspotmail.com
Fixes: f10e0010 ("net: xfrm: Add '_rcu' tag for rcu protected pointer in
netns_xfrm")
prev parent reply other threads:[~2019-03-19 20:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 16:02 WARNING: suspicious RCU usage in xfrm_alloc_userspi syzbot
2019-03-19 16:23 ` Eric Dumazet
2019-03-20 0:55 ` Su Yanjun <suyj.fnst@cn.fujitsu.com>
2019-03-19 20:59 ` 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=0000000000003ff5a5058478c6c4@google.com \
--to=syzbot+59752237f7ab21c3f3c3@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=fw@strlen.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
--cc=suyj.fnst@cn.fujitsu.com \
--cc=syzkaller-bugs@googlegroups.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).