From: Simon Horman <horms@kernel.org>
To: Liang Jie <buaajxlj@163.com>
Cc: Kuniyuki Iwashima <kuniyu@amazon.com>,
Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Michal Luczaj <mhal@rbox.co>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Liang Jie <liangjie@lixiang.com>
Subject: Re: [PATCH net-next] af_unix: Refine UNIX domain sockets autobind identifier length
Date: Wed, 5 Feb 2025 18:11:48 +0000 [thread overview]
Message-ID: <20250205181148.GK554665@kernel.org> (raw)
In-Reply-To: <20250205060653.2221165-1-buaajxlj@163.com>
On Wed, Feb 05, 2025 at 02:06:53PM +0800, Liang Jie wrote:
> From: Liang Jie <liangjie@lixiang.com>
>
> Refines autobind identifier length for UNIX domain sockets, addressing
> issues of memory waste and code readability.
>
> The previous implementation in the unix_autobind function of UNIX domain
> sockets used hardcoded values such as 16, 6, and 5 for memory allocation
> and setting the length of the autobind identifier, which was not only
> inflexible but also led to reduced code clarity. Additionally, allocating
> 16 bytes of memory for the autobind path was excessive, given that only 6
> bytes were ultimately used.
>
> To mitigate these issues, introduces the following changes:
> - A new macro AUTOBIND_LEN is defined to clearly represent the total
> length of the autobind identifier, which improves code readability and
> maintainability. It is set to 6 bytes to accommodate the unique autobind
> process identifier.
> - Memory allocation for the autobind path is now precisely based on
> AUTOBIND_LEN, thereby preventing memory waste.
> - The sprintf() function call is updated to dynamically format the
> autobind identifier according to the defined length, further enhancing
> code consistency and readability.
>
> The modifications result in a leaner memory footprint and elevated code
> quality, ensuring that the functional aspect of autobind behavior in UNIX
> domain sockets remains intact.
>
> Signed-off-by: Liang Jie <liangjie@lixiang.com>
> ---
> net/unix/af_unix.c | 13 ++++++++++---
> 1 file changed, 10 insertions(+), 3 deletions(-)
>
> diff --git a/net/unix/af_unix.c b/net/unix/af_unix.c
> index 34945de1fb1f..5dcc55f2e3a1 100644
> --- a/net/unix/af_unix.c
> +++ b/net/unix/af_unix.c
> @@ -1186,6 +1186,13 @@ static struct sock *unix_find_other(struct net *net,
> return sk;
> }
>
> +/*
> + * Define the total length of the autobind identifier for UNIX domain sockets.
> + * - The first byte distinguishes abstract sockets from filesystem-based sockets.
> + * - The subsequent five bytes store a unique identifier for the autobinding process.
> + */
> +#define AUTOBIND_LEN 6
> +
> static int unix_autobind(struct sock *sk)
> {
> struct unix_sock *u = unix_sk(sk);
> @@ -1204,11 +1211,11 @@ static int unix_autobind(struct sock *sk)
>
> err = -ENOMEM;
> addr = kzalloc(sizeof(*addr) +
> - offsetof(struct sockaddr_un, sun_path) + 16, GFP_KERNEL);
> + offsetof(struct sockaddr_un, sun_path) + AUTOBIND_LEN, GFP_KERNEL);
Hi Liang Jie,
1. While we are here, can we try to move this code to respect
the preference for lines 80 columns wide or less in Networking code?
e.g.
addr = kzalloc(sizeof(*addr) + offsetof(struct sockaddr_un, sun_path) +
AUTOBIND_LEN, GFP_KERNEL);
2. More importantly, this allocates AUTOBIND_LEN bytes for sun_path.
However, because the sprintf() will append a trailing '\0' it will
write up to AUTOBIND_LEN (that is, AUTOBIND_LEN - 1 + 1) bytes
at an offset of 1 to sun_path. IOW, the write may be one byte larger
than the buffer with the '\0' overflowing.
Flagged by W=1 build with gcc-14
> if (!addr)
> goto out;
>
> - addr->len = offsetof(struct sockaddr_un, sun_path) + 6;
> + addr->len = offsetof(struct sockaddr_un, sun_path) + AUTOBIND_LEN;
> addr->name->sun_family = AF_UNIX;
> refcount_set(&addr->refcnt, 1);
>
> @@ -1217,7 +1224,7 @@ static int unix_autobind(struct sock *sk)
> lastnum = ordernum & 0xFFFFF;
> retry:
> ordernum = (ordernum + 1) & 0xFFFFF;
> - sprintf(addr->name->sun_path + 1, "%05x", ordernum);
> + sprintf(addr->name->sun_path + 1, "%0*x", AUTOBIND_LEN - 1, ordernum);
>
> new_hash = unix_abstract_hash(addr->name, addr->len, sk->sk_type);
> unix_table_double_lock(net, old_hash, new_hash);
--
pw-bot: changes-requested
next prev parent reply other threads:[~2025-02-05 18:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 6:06 [PATCH net-next] af_unix: Refine UNIX domain sockets autobind identifier length Liang Jie
2025-02-05 8:28 ` Kuniyuki Iwashima
2025-02-05 10:09 ` Liang Jie
2025-02-06 4:01 ` Kuniyuki Iwashima
2025-02-06 4:27 ` Liang Jie
2025-02-06 19:20 ` David Laight
2025-02-05 18:11 ` Simon Horman [this message]
2025-02-06 6:49 ` kernel test robot
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=20250205181148.GK554665@kernel.org \
--to=horms@kernel.org \
--cc=buaajxlj@163.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=liangjie@lixiang.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhal@rbox.co \
--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 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.