All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Bryam Vargas <hexlabsecurity@proton.me>
Cc: kuba@kernel.org, dust.li@linux.alibaba.com, pabeni@redhat.com,
	edumazet@kernel.org, mjambigi@linux.ibm.com, davem@davemloft.net,
	sidraya@linux.ibm.com, alibuda@linux.alibaba.com,
	netdev@vger.kernel.org, ubraun@linux.ibm.com,
	linux-s390@vger.kernel.org, guwen@linux.alibaba.com,
	horms@kernel.org, linux-rdma@vger.kernel.org,
	hidayath@linux.ibm.com, tonylu@linux.alibaba.com,
	linux-kernel@vger.kernel.org, wenjia@linux.ibm.com
Subject: Re: [PATCH net] net/smc: queue the copied chunk when smc_tx_sendmsg() faults
Date: Wed, 21 Oct 2026 00:30:05 +0000	[thread overview]
Message-ID: <179254260529.285569.7327576902059914467.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261013-b4-disp-872a3689-v1-1-2a4c63b04761@proton.me>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Tue, 13 Oct 2026 15:45:01 -0500 you wrote:
> From: Bryam Vargas <hexlabsecurity@proton.me>
> 
> When a send wraps the end of the send buffer, smc_tx_sendmsg() copies
> the data in two chunks. If memcpy_from_msg() faults on the second one,
> smc_tx_sendmsg() returns send_done, which already counts the first
> chunk, but leaves tx_curs_prep and sndbuf_space as they were. send()
> reports bytes the peer never receives, and the next send() overwrites
> them. Any caller can hit this on its own stream with a buffer whose
> tail is unreadable.
> 
> [...]

Here is the summary with links:
  - [net] net/smc: queue the copied chunk when smc_tx_sendmsg() faults
    https://git.kernel.org/netdev/net/c/c0703534b223

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-10-21  0:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13 20:45 [PATCH net] net/smc: queue the copied chunk when smc_tx_sendmsg() faults Bryam Vargas via B4 Relay
2026-10-13 20:45 ` Bryam Vargas
2026-10-13 20:49 ` netdev-bot+sinfo
2026-10-13 20:52 ` sashiko-bot
2026-10-21  0:30 ` 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=179254260529.285569.7327576902059914467.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=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.