From: Joe Damato <jdamato@fastly.com>
To: Adrian Huang <adrianhuang0701@gmail.com>
Cc: Kuniyuki Iwashima <kuniyu@amazon.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Adrian Huang <ahuang12@lenovo.com>
Subject: Re: [PATCH v2 1/1] af_unix: Fix memory leak in unix_dgram_sendmsg()
Date: Mon, 24 Feb 2025 22:02:28 -0500 [thread overview]
Message-ID: <Z70yxC3uHE6R_KOu@LQ3V64L9R2> (raw)
In-Reply-To: <20250225021457.1824-1-ahuang12@lenovo.com>
On Tue, Feb 25, 2025 at 10:14:57AM +0800, Adrian Huang wrote:
> From: Adrian Huang <ahuang12@lenovo.com>
>
> After running the 'sendmsg02' program of Linux Test Project (LTP),
> kmemleak reports the following memory leak:
>
> # cat /sys/kernel/debug/kmemleak
> unreferenced object 0xffff888243866800 (size 2048):
> comm "sendmsg02", pid 67, jiffies 4294903166
> hex dump (first 32 bytes):
> 00 00 00 00 00 00 00 00 5e 00 00 00 00 00 00 00 ........^.......
> 01 00 07 40 00 00 00 00 00 00 00 00 00 00 00 00 ...@............
> backtrace (crc 7e96a3f2):
> kmemleak_alloc+0x56/0x90
> kmem_cache_alloc_noprof+0x209/0x450
> sk_prot_alloc.constprop.0+0x60/0x160
> sk_alloc+0x32/0xc0
> unix_create1+0x67/0x2b0
> unix_create+0x47/0xa0
> __sock_create+0x12e/0x200
> __sys_socket+0x6d/0x100
> __x64_sys_socket+0x1b/0x30
> x64_sys_call+0x7e1/0x2140
> do_syscall_64+0x54/0x110
> entry_SYSCALL_64_after_hwframe+0x76/0x7e
>
> Commit 689c398885cc ("af_unix: Defer sock_put() to clean up path in
> unix_dgram_sendmsg().") defers sock_put() in the error handling path.
> However, it fails to account for the condition 'msg->msg_namelen != 0',
> resulting in a memory leak when the code jumps to the 'lookup' label.
>
> Fix issue by calling sock_put() if 'msg->msg_namelen != 0' is met.
>
> Fixes: 689c398885cc ("af_unix: Defer sock_put() to clean up path in unix_dgram_sendmsg().")
> Signed-off-by: Adrian Huang <ahuang12@lenovo.com>
> ---
> Changelog v2:
> - Per Kuniyuki's suggestion: Remove 'else' statement
FYI according to netdev rules you should wait at least 24 hours
between repostings:
https://docs.kernel.org/process/maintainer-netdev.html#resending-after-review
That said:
Acked-by: Joe Damato <jdamato@fastly.com>
next prev parent reply other threads:[~2025-02-25 3:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 2:14 [PATCH v2 1/1] af_unix: Fix memory leak in unix_dgram_sendmsg() Adrian Huang
2025-02-25 3:02 ` Joe Damato [this message]
2025-02-25 19:09 ` Kuniyuki Iwashima
2025-02-27 3:30 ` patchwork-bot+netdevbpf
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=Z70yxC3uHE6R_KOu@LQ3V64L9R2 \
--to=jdamato@fastly.com \
--cc=adrianhuang0701@gmail.com \
--cc=ahuang12@lenovo.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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