All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+11dcfe6879155fbb6a4e@syzkaller.appspotmail.com>
To: andy@greyhouse.net, davem@davemloft.net, j.vosburgh@gmail.com,
	jarod@redhat.com, kuba@kernel.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
	vfalico@gmail.com
Subject: Re: WARNING: suspicious RCU usage in bond_ipsec_add_sa (2)
Date: Mon, 21 Sep 2020 07:06:09 -0700	[thread overview]
Message-ID: <0000000000002fe19f05afd35a45@google.com> (raw)
In-Reply-To: <000000000000fb6bf305afcfca61@google.com>

syzbot has bisected this issue to:

commit a3b658cfb66497525278cbf852913a04dbaae992
Author: Jarod Wilson <jarod@redhat.com>
Date:   Tue Jun 30 18:49:41 2020 +0000

    bonding: allow xfrm offload setup post-module-load

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=11eb70d3900000
start commit:   f13d783a MAINTAINERS: Update ibmveth maintainer
git tree:       net
final oops:     https://syzkaller.appspot.com/x/report.txt?x=13eb70d3900000
console output: https://syzkaller.appspot.com/x/log.txt?x=15eb70d3900000
kernel config:  https://syzkaller.appspot.com/x/.config?x=5ac0d21536db480b
dashboard link: https://syzkaller.appspot.com/bug?extid=11dcfe6879155fbb6a4e
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=17588ec5900000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=13db3281900000

Reported-by: syzbot+11dcfe6879155fbb6a4e@syzkaller.appspotmail.com
Fixes: a3b658cfb664 ("bonding: allow xfrm offload setup post-module-load")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

      reply	other threads:[~2020-09-21 14:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-21  9:51 WARNING: suspicious RCU usage in bond_ipsec_add_sa (2) syzbot
2020-09-21 14:06 ` 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=0000000000002fe19f05afd35a45@google.com \
    --to=syzbot+11dcfe6879155fbb6a4e@syzkaller.appspotmail.com \
    --cc=andy@greyhouse.net \
    --cc=davem@davemloft.net \
    --cc=j.vosburgh@gmail.com \
    --cc=jarod@redhat.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=vfalico@gmail.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.