From: patchwork-bot+netdevbpf@kernel.org
To: Wang Yan <wangyan01@kylinos.cn>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, shuah@kernel.org, horms@kernel.org,
lixiaoyan@google.com, netdev@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/net: fix EVP_MD_CTX leak in tcp_mmap
Date: Thu, 09 Jul 2026 08:40:10 +0000 [thread overview]
Message-ID: <178358641014.3333608.13910365421023945649.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260702025949.442523-1-wangyan01@kylinos.cn>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 2 Jul 2026 10:59:49 +0800 you wrote:
> In tcp_mmap.c, both child_thread() and main() allocate an EVP_MD_CTX
> via EVP_MD_CTX_new() when integrity checking is enabled, but neither
> function releases the context. child_thread() misses the free in its
> common cleanup block, and main() returns without freeing the context.
>
> This results in a SHA256 context leak on every run that uses the
> ‑i (integrity) option. Add the missing EVP_MD_CTX_free() calls to
> the appropriate cleanup paths to fix the leak.
>
> [...]
Here is the summary with links:
- selftests/net: fix EVP_MD_CTX leak in tcp_mmap
https://git.kernel.org/netdev/net/c/f4ef35efbb49
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-07-09 8:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 2:59 [PATCH] selftests/net: fix EVP_MD_CTX leak in tcp_mmap Wang Yan
2026-07-09 8: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=178358641014.3333608.13910365421023945649.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=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lixiaoyan@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=wangyan01@kylinos.cn \
/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