All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	weiwan@google.com, horms@kernel.org, caixinchen1@huawei.com,
	netdev@vger.kernel.org, edumazet@kernel.org
Subject: Re: [PATCH v2 net 0/2] net: fix SO_RESERVE_MEM socket type restriction and value bounds
Date: Tue, 29 Sep 2026 02:40:04 +0000	[thread overview]
Message-ID: <179064960453.229594.15099300870054423023.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260925135244.3715196-1-edumazet@google.com>

Hello:

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

On Fri, 25 Sep 2026 13:52:42 +0000 you wrote:
> This series fixes two issues with SO_RESERVE_MEM and adds a kselftest suite:
> 
> - Patch 1 restricts sock_reserve_memory() to TCP sockets (sk_is_tcp(sk))
>   instead of sk_has_account(sk), and caps the requested reservation to
>   SZ_1G in sk_setsockopt(SO_RESERVE_MEM).
> 
>   Currently, sk_has_account(sk) allows SO_RESERVE_MEM on UDP sockets,
>   where sk->sk_forward_alloc is protected by sk->sk_receive_queue.lock
>   rather than the socket lock, and udp_rmem_release() does not account
>   for sk_unused_reserved_mem(sk). Concurrent UDP packet processing and
>   setsockopt(SO_RESERVE_MEM) corrupt sk_forward_alloc and memcg
>   accounting. In addition, values near INT_MAX overflow 32-bit signed
>   int in sk_mem_pages(delta) and (pages << PAGE_SHIFT).
> 
> [...]

Here is the summary with links:
  - [v2,net,1/2] net: restrict SO_RESERVE_MEM to TCP sockets and cap max value
    https://git.kernel.org/netdev/net/c/37e02c42a00b
  - [v2,net,2/2] selftests/net: add SO_RESERVE_MEM test
    (no matching commit)

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-29  2:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-25 13:52 [PATCH v2 net 0/2] net: fix SO_RESERVE_MEM socket type restriction and value bounds Eric Dumazet
2026-09-25 13:52 ` [PATCH v2 net 1/2] net: restrict SO_RESERVE_MEM to TCP sockets and cap max value Eric Dumazet
2026-09-28 17:23   ` Wei Wang
2026-09-25 13:52 ` [PATCH v2 net 2/2] selftests/net: add SO_RESERVE_MEM test Eric Dumazet
2026-09-28 17:22   ` Wei Wang
2026-09-28 18:27     ` Eric Dumazet
2026-09-28 19:54   ` netdev-bot+sashiko
2026-09-28 20:03     ` Eric Dumazet
2026-09-28 20:18       ` Wei Wang
2026-09-29  2:40 ` 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=179064960453.229594.15099300870054423023.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=caixinchen1@huawei.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=edumazet@kernel.org \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=weiwan@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.