From: John Fastabend <john.fastabend@gmail.com>
To: syzbot <syzbot+320a3bc8d80f478c37e4@syzkaller.appspotmail.com>,
akpm@linux-foundation.org, andrii@kernel.org, anton@tuxera.com,
ast@kernel.org, bp@alien8.de, bpf@vger.kernel.org,
daniel@iogearbox.net, davem@davemloft.net, hpa@zytor.com,
jakub@cloudflare.com, jmattson@google.com,
john.fastabend@gmail.com, joro@8bytes.org, kafai@fb.com,
kpsingh@kernel.org, kuba@kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, lmb@cloudflare.com,
mingo@redhat.com, netdev@vger.kernel.org, pbonzini@redhat.com,
rkovhaev@gmail.com, seanjc@google.com, songliubraving@fb.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
torvalds@linux-foundation.org, vkuznets@redhat.com,
wanpengli@tencent.com, x86@kernel.org, yhs@fb.com
Subject: RE: [syzbot] WARNING: suspicious RCU usage in tcp_bpf_update_proto
Date: Tue, 06 Apr 2021 11:21:37 -0700 [thread overview]
Message-ID: <606ca6b12f544_f0242081@john-XPS-13-9370.notmuch> (raw)
In-Reply-To: <0000000000008872ff05bf40e4db@google.com>
syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 514e1150 net: x25: Queue received packets in the drivers i..
> git tree: net-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=112a8831d00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=7eff0f22b8563a5f
> dashboard link: https://syzkaller.appspot.com/bug?extid=320a3bc8d80f478c37e4
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1532d711d00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15f44c5ed00000
>
> The issue was bisected to:
>
> commit 4dfe6bd94959222e18d512bdf15f6bf9edb9c27c
> Author: Rustam Kovhaev <rkovhaev@gmail.com>
> Date: Wed Feb 24 20:00:30 2021 +0000
>
> ntfs: check for valid standard information attribute
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16207a81d00000
> final oops: https://syzkaller.appspot.com/x/report.txt?x=15207a81d00000
> console output: https://syzkaller.appspot.com/x/log.txt?x=11207a81d00000
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+320a3bc8d80f478c37e4@syzkaller.appspotmail.com
> Fixes: 4dfe6bd94959 ("ntfs: check for valid standard information attribute")
>
> =============================
> WARNING: suspicious RCU usage
> 5.12.0-rc4-syzkaller #0 Not tainted
> -----------------------------
> include/linux/skmsg.h:286 suspicious rcu_dereference_check() usage!
>
> other info that might help us debug this:
>
>
> rcu_scheduler_active = 2, debug_locks = 1
> 1 lock held by syz-executor383/8454:
> #0: ffff888013a99b48 (clock-AF_INET){++..}-{2:2}, at: sk_psock_drop+0x2c/0x460 net/core/skmsg.c:788
>
> stack backtrace:
> CPU: 1 PID: 8454 Comm: syz-executor383 Not tainted 5.12.0-rc4-syzkaller #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
> Call Trace:
> __dump_stack lib/dump_stack.c:79 [inline]
> dump_stack+0x141/0x1d7 lib/dump_stack.c:120
> sk_psock include/linux/skmsg.h:286 [inline]
> tcp_bpf_update_proto+0x530/0x5f0 net/ipv4/tcp_bpf.c:504
> sk_psock_restore_proto include/linux/skmsg.h:408 [inline]
> sk_psock_drop+0xdf/0x460 net/core/skmsg.c:789
> sk_psock_put include/linux/skmsg.h:446 [inline]
> tcp_bpf_recvmsg+0x42d/0x480 net/ipv4/tcp_bpf.c:208
The bisection is bogus, but we will get a fix for this ASAP. The real commit
is,
commit 8a59f9d1e3d4340659fdfee8879dc09a6f2546e1
Author: Cong Wang <cong.wang@bytedance.com>
Date: Tue Mar 30 19:32:31 2021 -0700
sock: Introduce sk->sk_prot->psock_update_sk_prot()
Thanks,
John
prev parent reply other threads:[~2021-04-06 18:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-05 22:05 [syzbot] WARNING: suspicious RCU usage in tcp_bpf_update_proto syzbot
2021-04-06 17:58 ` Cong Wang
2021-04-06 18:21 ` John Fastabend [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=606ca6b12f544_f0242081@john-XPS-13-9370.notmuch \
--to=john.fastabend@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=anton@tuxera.com \
--cc=ast@kernel.org \
--cc=bp@alien8.de \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=hpa@zytor.com \
--cc=jakub@cloudflare.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lmb@cloudflare.com \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkovhaev@gmail.com \
--cc=seanjc@google.com \
--cc=songliubraving@fb.com \
--cc=syzbot+320a3bc8d80f478c37e4@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@kernel.org \
--cc=yhs@fb.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).