From: John Fastabend <john.fastabend@gmail.com>
To: syzbot <syzbot+06dbd397158ec0ea4983@syzkaller.appspotmail.com>,
andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
cong.wang@bytedance.com, daniel@iogearbox.net,
davem@davemloft.net, dsahern@kernel.org, edumazet@google.com,
john.fastabend@gmail.com, kafai@fb.com, kpsingh@kernel.org,
kuba@kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev, nathan@kernel.org,
ndesaulniers@google.com, netdev@vger.kernel.org,
pabeni@redhat.com, songliubraving@fb.com,
syzkaller-bugs@googlegroups.com, trix@redhat.com, yhs@fb.com,
yoshfuji@linux-ipv6.org
Subject: RE: [syzbot] [net?] WARNING in tcp_recvmsg_locked (2)
Date: Tue, 05 Dec 2023 10:38:24 -0800 [thread overview]
Message-ID: <656f6e2050d_2df272086c@john.notmuch> (raw)
In-Reply-To: <0000000000004f438d060bc6e988@google.com>
syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 8470e4368b0f Merge branch 'net-cacheline-optimizations'
> git tree: net-next
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=12094286e80000
> kernel config: https://syzkaller.appspot.com/x/.config?x=f8715b6ede5c4b90
> dashboard link: https://syzkaller.appspot.com/bug?extid=06dbd397158ec0ea4983
> compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1247bee2e80000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1285243ce80000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/90007d08e178/disk-8470e436.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/b55270de1cdc/vmlinux-8470e436.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/2237d34b6fec/bzImage-8470e436.xz
>
> The issue was bisected to:
>
> commit 965b57b469a589d64d81b1688b38dcb537011bb0
> Author: Cong Wang <cong.wang@bytedance.com>
> Date: Wed Jun 15 16:20:12 2022 +0000
>
> net: Introduce a new proto_ops ->read_skb()
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1087c0d4e80000
> final oops: https://syzkaller.appspot.com/x/report.txt?x=1287c0d4e80000
> console output: https://syzkaller.appspot.com/x/log.txt?x=1487c0d4e80000
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+06dbd397158ec0ea4983@syzkaller.appspotmail.com
> Fixes: 965b57b469a5 ("net: Introduce a new proto_ops ->read_skb()")
>
> WARNING: CPU: 1 PID: 5130 at net/ipv4/tcp.c:2396 tcp_recvmsg_locked+0xa54/0x2490 net/ipv4/tcp.c:2396
I'll take a look. Thanks.
prev parent reply other threads:[~2023-12-05 18:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 17:53 [syzbot] [net?] WARNING in tcp_recvmsg_locked (2) syzbot
2023-12-05 18:38 ` 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=656f6e2050d_2df272086c@john.notmuch \
--to=john.fastabend@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=cong.wang@bytedance.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=songliubraving@fb.com \
--cc=syzbot+06dbd397158ec0ea4983@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=trix@redhat.com \
--cc=yhs@fb.com \
--cc=yoshfuji@linux-ipv6.org \
/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).