From: Nnamdi Onyeyiri <nnamdio@gmail.com>
To: bpf@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
horms@kernel.org, jakub@cloudflare.com, jiayuan.chen@linux.dev,
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, linux-kernel@vger.kernel.org,
emil@etsalapatis.com
Subject: Re: [PATCH v7 0/2] bpf, sockmap: handle spurious tcp_msg_wait_data() wakeup
Date: Wed, 5 Aug 2026 09:22:20 +0100 [thread overview]
Message-ID: <anLyIzAs9JBhZnhe@localhost.localdomain> (raw)
In-Reply-To: <20260721223807.75101-1-nnamdio@gmail.com>
On Tue, Jul 21, 2026 at 11:38:05PM +0100, Nnamdi Onyeyiri wrote:
> Spurious wakeups in tcp_msg_wait_data() aren'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 v7:
> - In tcp_bpf_recvmsg check for data in the TCP_CLOSE, !timeo and
> signal_pending branches.
> - Refactored changes to tcp_bpf_recvmsg to reduce duplication.
> - Increase the number of iterations in the selftests.
> - Documented selftests numeric constants.
> - Link to v6: https://patch.msgid.link/20260720171535.67867-1-nnamdio@gmail.com
>
> Changes in v6:
> - Closing the file descriptor in the selftest worker thread.
> - Ensuring the selftest loop breaks early for an error in the worker
> thread.
> - Added comments to selftest regarding focus on EAGAIN error.
> - Updated selftest commit message to imperative mood.
> - Link to v5: https://patch.msgid.link/20260717155348.54975-1-nnamdio@gmail.com
>
> Changes in v5:
> - Move selftest from net into bpf/prog_tests/sockmap_basic.c
> - Link to v4: https://patch.msgid.link/20260715213538.37229-1-nnamdio@gmail.com
>
> 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
>
> Changes in v3:
> - Added the sockmap_recvfrom selftest.
> - Link to v2: https://patch.msgid.link/alFRK66z45eDNZA7@localhost.localdomain
>
> 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
>
> Signed-off-by: Nnamdi Onyeyiri <nnamdio@gmail.com>
> ---
> Nnamdi Onyeyiri (2):
> bpf, sockmap: handle spurious tcp_msg_wait_data() wakeup
> selftests/bpf: add sockmap recvfrom EAGAIN selftest
>
> net/ipv4/tcp_bpf.c | 72 ++++++++--
> .../selftests/bpf/prog_tests/sockmap_basic.c | 136 ++++++++++++++++++
> 2 files changed, 199 insertions(+), 9 deletions(-)
>
> --
> 2.52.0
>
Hi all, just wondering if you need anything more from me on this?
next prev parent reply other threads:[~2026-08-05 8:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 22:38 [PATCH v7 0/2] bpf, sockmap: handle spurious tcp_msg_wait_data() wakeup Nnamdi Onyeyiri
2026-07-21 22:38 ` [PATCH v7 1/2] " Nnamdi Onyeyiri
2026-07-21 22:55 ` sashiko-bot
2026-07-22 11:01 ` Jakub Sitnicki
2026-07-22 11:22 ` Nnamdi Onyeyiri
2026-07-21 22:38 ` [PATCH v7 2/2] selftests/bpf: add sockmap recvfrom EAGAIN selftest Nnamdi Onyeyiri
2026-08-05 8:22 ` Nnamdi Onyeyiri [this message]
2026-08-05 13:51 ` [PATCH v7 0/2] bpf, sockmap: handle spurious tcp_msg_wait_data() wakeup Jiayuan Chen
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=anLyIzAs9JBhZnhe@localhost.localdomain \
--to=nnamdio@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=emil@etsalapatis.com \
--cc=horms@kernel.org \
--cc=jakub@cloudflare.com \
--cc=jiayuan.chen@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--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