From: Jiayuan Chen <jiayuan.chen@linux.dev>
To: Nnamdi Onyeyiri <nnamdio@gmail.com>, jiayuan.chen@linux.dev
Cc: bpf@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
horms@kernel.org, jakub@cloudflare.com, john.fastabend@gmail.com,
kuba@kernel.org, kuniyu@google.com, ncardwell@google.com,
netdev@vger.kernel.org, pabeni@redhat.com,
sashiko-reviews@lists.linux.dev
Subject: Re: [PATCH v4 0/2] bpf, sockmap: handle spurious tcp_msg_wait_data() wakeup
Date: Thu, 16 Jul 2026 09:30:30 +0800 [thread overview]
Message-ID: <95e690bf-2eed-469f-93ef-6ae3fb2a7162@linux.dev> (raw)
In-Reply-To: <20260715213538.37229-1-nnamdio@gmail.com>
On 7/16/26 5:35 AM, Nnamdi Onyeyiri wrote:
> Spurious wakeups in tcp_msg_wait_data() isn't being handled by
> tcp_bpf_recvmsg() and tcp_bpf_recvmsg_parser(), leading to unexpected
> EAGAIN errors returned by recvfrom()/recv(). Adding handling for the
> wakeup and a selftest.
>
> This issue was first discovered in an application that adds sockets to
> a sockmap as a way to view the received data. No redirects or any
> other operations are performed.
>
> Sashiko has noted a few other pre-existing issues in the same area
> (https://patch.msgid.link/20260714205118.17DB11F000E9@smtp.kernel.org)
> that can lead to EAGAIN in tcp_bpf_recvmsg() and
> tcp_bpf_recvmsg_parser(). A local run of Sashiko also identified a
> potential issue in tcp_bpf_recvmsg() handling zero-data FIN packets when
> the MSG_PEEK flag is set. To prevent this patchset from growing too
> large, I intend to submit follow up patches to address these once this
> one has been accepted.
>
> Changes in v2:
> - In tcp_bpf_recvmsg, handle signals and the socket closing in the loop.
> - Fix spurious wakeups when SO_RCVTIMEO has been set on the socket.
> - Link to v1: https://patch.msgid.link/ak_rR-Skd8Mvn4mH@localhost.localdomain
>
> Changes in v3:
> - Added the sockmap_recvfrom selftest.
> - Link to v2: https://patch.msgid.link/alFRK66z45eDNZA7@localhost.localdomain
>
> Changes in v4:
> - Fix potential data loss in tcp_bpf_recvmsg() when a FIN or RST has
> been received.
> - Check the return code of pthread_create() in the selftest.
> - Fix race caused by using EXPECT macros in a thread in selftest.
> - Link to v3: https://patch.msgid.link/20260714203927.32289-1-nnamdio@gmail.com
Please do not send a patch by replying to an old thread.
> Signed-off-by: Nnamdi Onyeyiri <nnamdio@gmail.com>
> ---
> Nnamdi Onyeyiri (2):
> bpf, sockmap: handle spurious tcp_msg_wait_data() wakeup
> bpf, sockmap: handle spurious tcp_msg_wait_data() wakeup
Please use a commit subject like "selftests/bpf: add selftest xxx" for
the selftest patch.
>
> net/ipv4/tcp_bpf.c | 69 +++-
> tools/testing/selftests/net/.gitignore | 2 +
> tools/testing/selftests/net/Makefile | 5 +
> .../selftests/net/sockmap_recvfrom.bpf.c | 31 ++
> .../testing/selftests/net/sockmap_recvfrom.c | 299 ++++++++++++++++++
Please use existing test frameworks such as sockmap_basic.c or
sockmap_strp.c.
next prev parent reply other threads:[~2026-07-16 1:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 18:43 [BUG] bpf, sockmap: spurious wakeup by tcp_msg_wait_data() causing unexpected EAGAIN in recvfrom() Nnamdi Onyeyiri
2026-07-09 18:55 ` sashiko-bot
2026-07-10 20:17 ` Nnamdi Onyeyiri
2026-07-13 4:14 ` Jiayuan Chen
2026-07-14 18:19 ` John Fastabend
2026-07-14 20:39 ` [PATCH v3 0/2] bpf, sockmap: handle spurious tcp_msg_wait_data() wakeup Nnamdi Onyeyiri
2026-07-14 20:39 ` [PATCH v3 1/2] " Nnamdi Onyeyiri
2026-07-14 20:51 ` sashiko-bot
2026-07-14 20:39 ` [PATCH v3 2/2] " Nnamdi Onyeyiri
2026-07-14 20:52 ` sashiko-bot
2026-07-15 21:35 ` [PATCH v4 0/2] " Nnamdi Onyeyiri
2026-07-15 21:35 ` [PATCH v4 1/2] " Nnamdi Onyeyiri
2026-07-15 21:35 ` [PATCH v4 2/2] " Nnamdi Onyeyiri
2026-07-15 21:47 ` sashiko-bot
2026-07-16 1:30 ` Jiayuan Chen [this message]
2026-07-14 18:16 ` [BUG] bpf, sockmap: spurious wakeup by tcp_msg_wait_data() causing unexpected EAGAIN in recvfrom() John Fastabend
2026-07-14 20:47 ` Nnamdi Onyeyiri
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=95e690bf-2eed-469f-93ef-6ae3fb2a7162@linux.dev \
--to=jiayuan.chen@linux.dev \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jakub@cloudflare.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=nnamdio@gmail.com \
--cc=pabeni@redhat.com \
--cc=sashiko-reviews@lists.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