[syzbot] WARNING: suspicious RCU usage (5)

14 views
Skip to first unread message

syzbot

unread,
Jun 17, 2022, 6:56:23 PM6/17/22
to linux-...@vger.kernel.org, net...@vger.kernel.org, syzkall...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: a5b00f5b78b7 Merge branch 'hns3-fixres'
git tree: net
console output: https://syzkaller.appspot.com/x/log.txt?x=105d68bbf00000
kernel config: https://syzkaller.appspot.com/x/.config?x=20ac3e0ebf0db3bd
dashboard link: https://syzkaller.appspot.com/bug?extid=9cbc6bed3a22f1d37395
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=143b22abf00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=125194eff00000

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+9cbc6b...@syzkaller.appspotmail.com

netdevsim netdevsim0 netdevsim0: set [1, 0] type 2 family 0 port 6081 - 0
netdevsim netdevsim0 netdevsim1: set [1, 0] type 2 family 0 port 6081 - 0
netdevsim netdevsim0 netdevsim2: set [1, 0] type 2 family 0 port 6081 - 0
netdevsim netdevsim0 netdevsim3: set [1, 0] type 2 family 0 port 6081 - 0
=============================
WARNING: suspicious RCU usage
5.19.0-rc1-syzkaller-00254-ga5b00f5b78b7 #0 Not tainted
-----------------------------
net/ipv6/addrconf


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches

syzbot

unread,
Jun 23, 2022, 3:35:15 AM6/23/22
to alob...@pm.me, b...@alien8.de, dan...@iogearbox.net, h...@zytor.com, jmat...@google.com, john.fa...@gmail.com, jo...@8bytes.org, k...@vger.kernel.org, linux-...@vger.kernel.org, mi...@redhat.com, net...@vger.kernel.org, pbon...@redhat.com, sea...@google.com, syzkall...@googlegroups.com, tg...@linutronix.de, vkuz...@redhat.com, wanp...@tencent.com, x...@kernel.org, xuan...@linux.alibaba.com
syzbot has bisected this issue to:

commit c2ff53d8049f30098153cd2d1299a44d7b124c57
Author: Xuan Zhuo <xuan...@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
Reported-by: syzbot+9cbc6b...@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

Xuan Zhuo

unread,
Jun 23, 2022, 4:33:11 AM6/23/22
to syzbot, alob...@pm.me, b...@alien8.de, dan...@iogearbox.net, h...@zytor.com, jmat...@google.com, john.fa...@gmail.com, jo...@8bytes.org, k...@vger.kernel.org, linux-...@vger.kernel.org, mi...@redhat.com, net...@vger.kernel.org, pbon...@redhat.com, sea...@google.com, syzkall...@googlegroups.com, tg...@linutronix.de, vkuz...@redhat.com, wanp...@tencent.com, x...@kernel.org
I think it's unlikely that my patch is causing the problem, because my patch is
very simple and doesn't have any effect on the kernel. I don't know if there is
something wrong.

I used the above config (make olddefconfig) to compile this commit, and it
crashed directly after starting it in qemu.

Thanks.

Paolo Bonzini

unread,
Jun 23, 2022, 4:54:54 AM6/23/22
to syzbot, Alexander Lobakin, Borislav Petkov, Daniel Borkmann, Anvin, H. Peter, Jim Mattson, John Fastabend, Joerg Roedel, kvm, Kernel Mailing List, Linux, Ingo Molnar, Networking, Sean Christopherson, syzkaller-bugs, Thomas Gleixner, Vitaly Kuznetsov, Wanpeng Li, the arch/x86 maintainers, xuan...@linux.alibaba.com
#syz fix: x86/kvm: Fix broken irq restoration in kvm_wait
Reply all
Reply to author
Forward
0 new messages