public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jiayuan Chen <jiayuan.chen@linux.dev>
Cc: bpf@vger.kernel.org, john.fastabend@gmail.com,
	jakub@cloudflare.com, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
	ncardwell@google.com, kuniyu@google.com, dsahern@kernel.org,
	andrii@kernel.org, eddyz87@gmail.com, ast@kernel.org,
	daniel@iogearbox.net, martin.lau@linux.dev, song@kernel.org,
	yonghong.song@linux.dev, kpsingh@kernel.org, sdf@fomichev.me,
	haoluo@google.com, jolsa@kernel.org, shuah@kernel.org,
	mhal@rbox.co, cong.wang@bytedance.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH bpf-next v9 0/3] bpf: Fix FIONREAD and copied_seq issues
Date: Tue, 27 Jan 2026 17:20:09 +0000	[thread overview]
Message-ID: <176953440910.945615.5240442156824844283.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260124113314.113584-1-jiayuan.chen@linux.dev>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Sat, 24 Jan 2026 19:32:42 +0800 you wrote:
> syzkaller reported a bug [1] where a socket using sockmap, after being
> unloaded, exposed incorrect copied_seq calculation. The selftest I
> provided can be used to reproduce the issue reported by syzkaller.
> 
> TCP recvmsg seq # bug 2: copied E92C873, seq E68D125, rcvnxt E7CEB7C, fl 40
> WARNING: CPU: 1 PID: 5997 at net/ipv4/tcp.c:2724 tcp_recvmsg_locked+0xb2f/0x2910 net/ipv4/tcp.c:2724
> Call Trace:
>  <TASK>
>  receive_fallback_to_copy net/ipv4/tcp.c:1968 [inline]
>  tcp_zerocopy_receive+0x131a/0x2120 net/ipv4/tcp.c:2200
>  do_tcp_getsockopt+0xe28/0x26c0 net/ipv4/tcp.c:4713
>  tcp_getsockopt+0xdf/0x100 net/ipv4/tcp.c:4812
>  do_sock_getsockopt+0x34d/0x440 net/socket.c:2421
>  __sys_getsockopt+0x12f/0x260 net/socket.c:2450
>  __do_sys_getsockopt net/socket.c:2457 [inline]
>  __se_sys_getsockopt net/socket.c:2454 [inline]
>  __x64_sys_getsockopt+0xbd/0x160 net/socket.c:2454
>  do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
>  do_syscall_64+0xcd/0xfa0 arch/x86/entry/syscall_64.c:94
>  entry_SYSCALL_64_after_hwframe+0x77/0x7f
> 
> [...]

Here is the summary with links:
  - [bpf-next,v9,1/3] bpf, sockmap: Fix incorrect copied_seq calculation
    https://git.kernel.org/bpf/bpf-next/c/b40cc5adaa80
  - [bpf-next,v9,2/3] bpf, sockmap: Fix FIONREAD for sockmap
    https://git.kernel.org/bpf/bpf-next/c/929e30f93125
  - [bpf-next,v9,3/3] bpf, selftest: Add tests for FIONREAD and copied_seq
    https://git.kernel.org/bpf/bpf-next/c/17e2ce02bf56

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-01-27 17:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-24 11:32 [PATCH bpf-next v9 0/3] bpf: Fix FIONREAD and copied_seq issues Jiayuan Chen
2026-01-24 11:32 ` [PATCH bpf-next v9 1/3] bpf, sockmap: Fix incorrect copied_seq calculation Jiayuan Chen
2026-01-24 11:32 ` [PATCH bpf-next v9 2/3] bpf, sockmap: Fix FIONREAD for sockmap Jiayuan Chen
2026-01-25  2:10   ` Alexei Starovoitov
2026-01-26 10:53   ` Jakub Sitnicki
2026-01-24 11:32 ` [PATCH bpf-next v9 3/3] bpf, selftest: Add tests for FIONREAD and copied_seq Jiayuan Chen
2026-01-26 10:59   ` Jakub Sitnicki
2026-01-27 17:20 ` patchwork-bot+netdevbpf [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=176953440910.945615.5240442156824844283.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --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=eddyz87@gmail.com \
    --cc=edumazet@google.com \
    --cc=haoluo@google.com \
    --cc=horms@kernel.org \
    --cc=jakub@cloudflare.com \
    --cc=jiayuan.chen@linux.dev \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=mhal@rbox.co \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sdf@fomichev.me \
    --cc=shuah@kernel.org \
    --cc=song@kernel.org \
    --cc=yonghong.song@linux.dev \
    /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