mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Daehyeon Ko <4ncienth@gmail.com>
Cc: edumazet@kernel.org, ncardwell@google.com, kuniyu@google.com,
	davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	horms@kernel.org, almasrymina@google.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] tcp: reject net_iov in zerocopy receive mapping hints
Date: Fri, 02 Oct 2026 20:10:05 +0000	[thread overview]
Message-ID: <179097180553.3568371.386085043073981304.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260930102524.1659847-1-4ncienth@gmail.com>

Hello:

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

On Wed, 30 Sep 2026 19:25:24 +0900 you wrote:
> After copying a readable prefix, receive_fallback_to_copy() asks
> tcp_zerocopy_set_hint_for_skb() where page mapping can resume. If the
> next skb is unreadable, find_next_mappable_frag() passes its net_iov
> fragment to can_map_frag().
> 
> skb_frag_page() returns NULL for a net_iov, but can_map_frag()
> dereferences it in PageCompound(). A v7.2 KASAN run on a connected TCP
> socket with 64 readable bytes followed by a 4096-byte NET_IOV_DMABUF
> fragment reported:
> 
> [...]

Here is the summary with links:
  - [net] tcp: reject net_iov in zerocopy receive mapping hints
    https://git.kernel.org/netdev/net/c/8b1f0af1fd5f

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-02 20:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30 10:25 Daehyeon Ko
2026-09-30 16:12 ` Mina Almasry
2026-10-02 20: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=179097180553.3568371.386085043073981304.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=4ncienth@gmail.com \
    --cc=almasrymina@google.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncardwell@google.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®