From: patchwork-bot+netdevbpf@kernel.org
To: Bryam Vargas <hexlabsecurity@proton.me>
Cc: dust.li@linux.alibaba.com, alibuda@linux.alibaba.com,
mjambigi@linux.ibm.com, sidraya@linux.ibm.com,
davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@kernel.org, linux-s390@vger.kernel.org,
guwen@linux.alibaba.com, linux-rdma@vger.kernel.org,
tonylu@linux.alibaba.com, wenjia@linux.ibm.com,
netdev@vger.kernel.org, raspl@linux.ibm.com,
hidayath@linux.ibm.com, horms@kernel.org, ubraun@linux.ibm.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2] net/smc: don't spin in smc_rx_recvmsg() while a pipe holds spliced data
Date: Thu, 05 Nov 2026 10:10:04 +0000 [thread overview]
Message-ID: <179387340405.3565783.10479272570067778591.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261029-b4-disp-da7f8e6a-v2-1-9052904adf72@proton.me>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 29 Oct 2026 03:03:33 -0500 you wrote:
> From: Bryam Vargas <hexlabsecurity@proton.me>
>
> While bytes spliced off the RMB are still in a pipe, recvmsg() waits
> for the pipe to release them before it copies the data behind them.
> The path to that wait skips the timeout and signal checks, and
> smc_rx_wait() returns at once on RCV_SHUTDOWN. With a signal pending,
> after SHUT_RD, or once the peer closes or shuts down writing,
> recvmsg() spins on a CPU until the pipe is drained, and SIGKILL cannot
> stop it. MSG_DONTWAIT and an expired SO_RCVTIMEO wait there too
> instead of returning -EAGAIN.
>
> [...]
Here is the summary with links:
- [net,v2] net/smc: don't spin in smc_rx_recvmsg() while a pipe holds spliced data
https://git.kernel.org/netdev/net/c/8288ba942cfd
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-05 10:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 8:03 [PATCH net v2] net/smc: don't spin in smc_rx_recvmsg() while a pipe holds spliced data Bryam Vargas via B4 Relay
2026-10-29 8:03 ` Bryam Vargas
2026-10-29 8:06 ` netdev-bot+sinfo
2026-10-29 8:15 ` sashiko-bot
2026-11-03 14:18 ` Paolo Abeni
2026-11-04 16:56 ` Dust Li
2026-11-04 17:00 ` Dust Li
2026-11-05 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=179387340405.3565783.10479272570067778591.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alibuda@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=dust.li@linux.alibaba.com \
--cc=edumazet@kernel.org \
--cc=guwen@linux.alibaba.com \
--cc=hexlabsecurity@proton.me \
--cc=hidayath@linux.ibm.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mjambigi@linux.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=raspl@linux.ibm.com \
--cc=sidraya@linux.ibm.com \
--cc=tonylu@linux.alibaba.com \
--cc=ubraun@linux.ibm.com \
--cc=wenjia@linux.ibm.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.