All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
	mason@kernel.org, kylebot@openai.com, willemb@google.com
Subject: Re: [PATCH net] net: skbuff: uncharge trimmed zerocopy frags on error
Date: Tue, 10 Nov 2026 23:30:05 +0000	[thread overview]
Message-ID: <179435340543.113833.8281856662943688738.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261105223512.3647504-1-willemdebruijn.kernel@gmail.com>

Hello:

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

On Thu,  5 Nov 2026 17:35:06 -0500 you wrote:
> From: Chris Mason <mason@kernel.org>
> 
> __zerocopy_sg_from_iter() accounts for the frags that it adds even when
> it returns an error: it adds the growth of skb->truesize to
> sk_wmem_queued and, unless the skb is pure zerocopy, charges it to the
> socket.
> 
> [...]

Here is the summary with links:
  - [net] net: skbuff: uncharge trimmed zerocopy frags on error
    https://git.kernel.org/netdev/net/c/8b67debdfbf6

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-11-10 23:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-05 22:35 [PATCH net] net: skbuff: uncharge trimmed zerocopy frags on error Willem de Bruijn
2026-11-05 22:37 ` netdev-bot+sinfo
2026-11-05 22:39   ` Willem de Bruijn
2026-11-10 23:22     ` Jakub Kicinski
2026-11-10 23: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=179435340543.113833.8281856662943688738.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kylebot@openai.com \
    --cc=mason@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=willemb@google.com \
    --cc=willemdebruijn.kernel@gmail.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.