From: patchwork-bot+netdevbpf@kernel.org
To: Jens Axboe <axboe@kernel.dk>
Cc: netdev@vger.kernel.org, edumazet@kernel.org, kuniyu@google.com,
pabeni@redhat.com, willemb@google.com, kuba@kernel.org
Subject: Re: [PATCH net v2] net: leave O_NONBLOCK to the sendmsg and recvmsg syscalls
Date: Wed, 11 Nov 2026 10:10:04 +0000 [thread overview]
Message-ID: <179439180477.841340.17728656628315045558.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <691880db-d6c6-4147-8509-93fc76125d29@kernel.dk>
Hello:
This patch was applied to netdev/net.git (main)
by Dave Miller <davem@davem-thinkpadp1gen8.ibmlond.csb>:
On Fri, 6 Nov 2026 16:50:46 -0700 you wrote:
> ____sys_sendmsg() and ____sys_recvmsg() turn O_NONBLOCK on the socket
> into MSG_DONTWAIT. That is right for the system calls, but io_uring uses
> __sys_sendmsg_sock() and __sys_recvmsg_sock() for a blocking attempt
> from io-wq as well, after the non-blocking attempts with MSG_DONTWAIT
> have failed. On an O_NONBLOCK socket that attempt can't block either and
> the request completes with -EAGAIN, unlike IORING_OP_SEND and RECV,
> which call sock_sendmsg() and sock_recvmsg() directly and don't look at
> O_NONBLOCK at all.
>
> [...]
Here is the summary with links:
- [net,v2] net: leave O_NONBLOCK to the sendmsg and recvmsg syscalls
https://git.kernel.org/netdev/net/c/bdc350ddbcbe
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-11-11 10:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 23:50 [PATCH net v2] net: leave O_NONBLOCK to the sendmsg and recvmsg syscalls Jens Axboe
2026-11-11 10:10 ` 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=179439180477.841340.17728656628315045558.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=axboe@kernel.dk \
--cc=edumazet@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox