public inbox for kernel-tls-handshake@lists.linux.dev
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Ruan Jinjie <ruanjinjie@huawei.com>
Cc: kernel-tls-handshake@lists.linux.dev, netdev@vger.kernel.org,
	chuck.lever@oracle.com, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com
Subject: Re: [PATCH] net/handshake: Fix memory leak in __sock_create() and sock_alloc_file()
Date: Wed, 20 Sep 2023 11:00:22 +0000	[thread overview]
Message-ID: <169520762284.31903.2503841633352666153.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230919104406.847875-1-ruanjinjie@huawei.com>

Hello:

This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:

On Tue, 19 Sep 2023 18:44:06 +0800 you wrote:
> When making CONFIG_DEBUG_KMEMLEAK=y and CONFIG_DEBUG_KMEMLEAK_AUTO_SCAN=y,
> modprobe handshake-test and then rmmmod handshake-test, the below memory
> leak is detected.
> 
> The struct socket_alloc which is allocated by alloc_inode_sb() in
> __sock_create() is not freed. And the struct dentry which is allocated
> by __d_alloc() in sock_alloc_file() is not freed.
> 
> [...]

Here is the summary with links:
  - net/handshake: Fix memory leak in __sock_create() and sock_alloc_file()
    https://git.kernel.org/netdev/net/c/4a0f07d71b04

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2023-09-20 11:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-19 10:44 [PATCH] net/handshake: Fix memory leak in __sock_create() and sock_alloc_file() Jinjie Ruan
2023-09-20 11: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=169520762284.31903.2503841633352666153.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kernel-tls-handshake@lists.linux.dev \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=ruanjinjie@huawei.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