All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+bfb3cbc2e9467b566c8b@syzkaller.appspotmail.com>
To: davem@davemloft.net, 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_get_spdinfo
Date: Tue, 19 Mar 2019 13:57:00 -0700	[thread overview]
Message-ID: <0000000000001224fa058478bf4b@google.com> (raw)
In-Reply-To: <0000000000008a14a5058474a025@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=166cae2b200000
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=156cae2b200000
console output: https://syzkaller.appspot.com/x/log.txt?x=116cae2b200000
kernel config:  https://syzkaller.appspot.com/x/.config?x=59cd5d43b5df6955
dashboard link: https://syzkaller.appspot.com/bug?extid=bfb3cbc2e9467b566c8b
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=12af288b200000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=147162a3200000

Reported-by: syzbot+bfb3cbc2e9467b566c8b@syzkaller.appspotmail.com
Fixes: f10e0010 ("net: xfrm: Add '_rcu' tag for rcu protected pointer in  
netns_xfrm")

      reply	other threads:[~2019-03-19 20:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-19 16:02 WARNING: suspicious RCU usage in xfrm_get_spdinfo syzbot
2019-03-19 20:57 ` 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=0000000000001224fa058478bf4b@google.com \
    --to=syzbot+bfb3cbc2e9467b566c8b@syzkaller.appspotmail.com \
    --cc=davem@davemloft.net \
    --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 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.