All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Pavel Begunkov <asml.silence@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org, netdev@vger.kernel.org,
	almasrymina@google.com
Subject: Re: [PATCH net v2 1/1] tcp: reject non zerocopy devmem tx
Date: Thu, 10 Sep 2026 12:50:20 +0000	[thread overview]
Message-ID: <178904462058.1411984.7973332298016907409.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <fdc2478d8f21268d7078556409887d8e6ba0ad32.1788529053.git.asml.silence@gmail.com>

Hello:

This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Fri,  4 Sep 2026 14:43:07 +0100 you wrote:
> Devmem tcp tx doesn't work without zero-copy, however it's not currently
> enforced if NETIF_F_SG isn't present. In this case, tcp_sendmsg_locked()
> will try the copy path and try to copy data from an iovec which consists
> of offsets into the dma-buf and would normally fail. Moreover,
> d9c56501c72fd ("net: tcp: block mixing readable and unreadable frags")
> relies on that and assumes that the devmem binding is present IFF we're
> using the zero-copy path, which can be used to mix net-iov and pages in
> a single skb, and break invariants. Let's reject devmem tx without
> zero-copy.
> 
> [...]

Here is the summary with links:
  - [net,v2,1/1] tcp: reject non zerocopy devmem tx
    https://git.kernel.org/netdev/net/c/125755776bc6

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-09-10 12:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04 13:43 [PATCH net v2 1/1] tcp: reject non zerocopy devmem tx Pavel Begunkov
2026-09-09 13:45 ` netdev-bot+sashiko
2026-09-09 15:57   ` Mina Almasry
2026-09-10 12:44     ` Paolo Abeni
2026-09-10 12:51     ` Pavel Begunkov
2026-09-10 12:50 ` 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=178904462058.1411984.7973332298016907409.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=almasrymina@google.com \
    --cc=asml.silence@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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.