From: Nnamdi Onyeyiri <nnamdio@gmail.com>
To: John Fastabend <john.fastabend@gmail.com>
Cc: bpf@vger.kernel.org
Subject: Re: [BUG] bpf, sockmap: spurious wakeup by tcp_msg_wait_data() causing unexpected EAGAIN in recvfrom()
Date: Tue, 14 Jul 2026 21:47:22 +0100 [thread overview]
Message-ID: <alafJdu0y1IdYg_w@localhost.localdomain> (raw)
In-Reply-To: <alZ8nmJlkhguOG5v@john-p8>
On Tue, Jul 14, 2026 at 11:16:27AM -0700, John Fastabend wrote:
> If its breaking/changing applications I think its a bug. Can you submit
> the patch below? We had something similar with ioctl FIONREAD behavior
> as well that was recently fixed.
>
> Thanks,
> John
Yes, this was first discovered by a python application breaking (an
EAGAIN error causes a BlockingIOError exception). I have submitted the change
as a patchset here: https://patch.msgid.link/20260714203927.32289-1-nnamdio@gmail.com
This is my first time submitting a patch, so I wasn't sure if the selftest belongs
in bpf or net. I've put it in net. Please let me know if this should be moved.
Thanks,
Nnamdi.
prev parent reply other threads:[~2026-07-14 20:47 UTC|newest]
Thread overview: 12+ 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-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 [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=alafJdu0y1IdYg_w@localhost.localdomain \
--to=nnamdio@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=john.fastabend@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.