From: syzbot <syzbot+9cbc6bed3a22f1d37395@syzkaller.appspotmail.com>
To: alobakin@pm.me, bp@alien8.de, daniel@iogearbox.net,
hpa@zytor.com, jmattson@google.com, john.fastabend@gmail.com,
joro@8bytes.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, mingo@redhat.com,
netdev@vger.kernel.org, pbonzini@redhat.com, seanjc@google.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
vkuznets@redhat.com, wanpengli@tencent.com, x86@kernel.org,
xuanzhuo@linux.alibaba.com
Subject: Re: [syzbot] WARNING: suspicious RCU usage (5)
Date: Thu, 23 Jun 2022 00:35:13 -0700 [thread overview]
Message-ID: <0000000000008b8cd205e2187ea2@google.com> (raw)
In-Reply-To: <000000000000b9edeb05e1aca987@google.com>
syzbot has bisected this issue to:
commit c2ff53d8049f30098153cd2d1299a44d7b124c57
Author: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Date: Thu Feb 18 20:50:02 2021 +0000
net: Add priv_flags for allow tx skb without linear
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11596838080000
start commit: a5b00f5b78b7 Merge branch 'hns3-fixres'
git tree: net
final oops: https://syzkaller.appspot.com/x/report.txt?x=13596838080000
console output: https://syzkaller.appspot.com/x/log.txt?x=15596838080000
kernel config: https://syzkaller.appspot.com/x/.config?x=20ac3e0ebf0db3bd
dashboard link: https://syzkaller.appspot.com/bug?extid=9cbc6bed3a22f1d37395
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=143b22abf00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=125194eff00000
Reported-by: syzbot+9cbc6bed3a22f1d37395@syzkaller.appspotmail.com
Fixes: c2ff53d8049f ("net: Add priv_flags for allow tx skb without linear")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2022-06-23 7:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 22:56 [syzbot] WARNING: suspicious RCU usage (5) syzbot
2022-06-23 7:35 ` syzbot [this message]
2022-06-23 8:22 ` Xuan Zhuo
2022-06-23 8:54 ` Paolo Bonzini
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=0000000000008b8cd205e2187ea2@google.com \
--to=syzbot+9cbc6bed3a22f1d37395@syzkaller.appspotmail.com \
--cc=alobakin@pm.me \
--cc=bp@alien8.de \
--cc=daniel@iogearbox.net \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=john.fastabend@gmail.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@kernel.org \
--cc=xuanzhuo@linux.alibaba.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.