From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
weiwan@google.com, horms@kernel.org, netdev@vger.kernel.org,
edumazet@google.com
Subject: Re: [PATCH v3 net-next] selftests/net: add SO_RESERVE_MEM test
Date: Tue, 06 Oct 2026 00:00:12 +0000 [thread overview]
Message-ID: <179124481277.1944959.10542295544983932360.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261001192137.309983-1-edumazet@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 1 Oct 2026 21:21:37 +0200 you wrote:
> Add a kselftest suite covering SO_RESERVE_MEM behavior:
> - Reject unsupported socket types (UDP/SOCK_DGRAM, UNIX/SOCK_STREAM,
> SOCK_RAW, MPTCP) with EOPNOTSUPP, for both zero and non-zero values.
> - Validate bounds (negative values and values > SZ_1G return EINVAL).
> - Verify reserve adjustments (increase, decrease, page rounding, and
> reset to 0) and corresponding sk_meminfo[SK_MEMINFO_FWD_ALLOC] changes
> via getsockopt(SO_MEMINFO).
> - Exercise cgroup v2 memory.max enforcement returning ENOMEM when the
> requested reservation exceeds the cgroup limit.
> - Verify that a child socket returned by accept() starts with a 0
> reserve even when its parent listener configured a non-zero
> SO_RESERVE_MEM.
> - Verify reserve retention across TCP send/receive/ACK cycles.
>
> [...]
Here is the summary with links:
- [v3,net-next] selftests/net: add SO_RESERVE_MEM test
https://git.kernel.org/netdev/net-next/c/095dc989f002
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-10-06 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 19:21 [PATCH v3 net-next] selftests/net: add SO_RESERVE_MEM test Eric Dumazet
2026-10-06 0:00 ` 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=179124481277.1944959.10542295544983932360.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox