All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Octavian Purdila <tavip@google.com>
Cc: edumazet@kernel.org, ncardwell@google.com, kuniyu@google.com,
	davem@davemloft.net, dsahern@kernel.org, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org, shakeel.butt@linux.dev,
	willemb@google.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v5] tcp: do not let tcp_collapse() drive sk_forward_alloc negative
Date: Mon, 02 Nov 2026 10:30:05 +0000	[thread overview]
Message-ID: <179361540591.3925787.2665655374452049262.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261028190820.2917252-1-tavip@google.com>

Hello:

This patch was applied to netdev/net.git (main)
by Dave Miller <davem@davem-thinkpadp1gen8.ibmlond.csb>:

On Wed, 28 Oct 2026 19:08:20 +0000 you wrote:
> From: Eric Dumazet <edumazet@kernel.org>
> 
> tcp_collapse() charges each newly allocated skb with skb_set_owner_r()
> before the skbs it replaces are freed, without scheduling memory first.
> 
> Since sk_mem_uncharge() reclaims eagerly, sk->sk_forward_alloc has no
> cushion and can become negative. This can be durable when the collapsed
> skbs had a high payload/truesize ratio or were partially read, because
> the new skbs can have a bigger total truesize than the old ones.
> 
> [...]

Here is the summary with links:
  - [net,v5] tcp: do not let tcp_collapse() drive sk_forward_alloc negative
    https://git.kernel.org/netdev/net/c/031c403d13e5

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-28 19:08 [PATCH net v5] tcp: do not let tcp_collapse() drive sk_forward_alloc negative Octavian Purdila
2026-10-28 19:11 ` netdev-bot+sinfo
2026-11-01 19:24 ` netdev-bot+sashiko
2026-11-02 10: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=179361540591.3925787.2665655374452049262.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --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 \
    --cc=shakeel.butt@linux.dev \
    --cc=tavip@google.com \
    --cc=willemb@google.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.