From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <enjuk@amazon.com>
Cc: <davem@davemloft.net>, <edumazet@google.com>,
<gnaaman@drivenets.com>, <horms@kernel.org>,
<joel.granados@kernel.org>, <kohei.enju@gmail.com>,
<kuba@kernel.org>, <kuniyu@amazon.com>,
<linux-kernel@vger.kernel.org>, <lizetao1@huawei.com>,
<netdev@vger.kernel.org>, <pabeni@redhat.com>
Subject: Re: [PATCH net-next v1] neighbour: Replace kvzalloc() with kzalloc() when GFP_ATOMIC is specified
Date: Sun, 16 Feb 2025 11:06:42 -0800 [thread overview]
Message-ID: <20250216190642.31169-1-kuniyu@amazon.com> (raw)
In-Reply-To: <20250216163016.57444-1-enjuk@amazon.com>
From: Kohei Enju <enjuk@amazon.com>
Date: Mon, 17 Feb 2025 01:30:16 +0900
> Replace kvzalloc()/kvfree() with kzalloc()/kfree() when GFP_ATOMIC is
> specified, since kvzalloc() doesn't support non-sleeping allocations such
> as GFP_ATOMIC.
>
> With incompatible gfp flags, kvzalloc() never falls back to the vmalloc
> path and returns immediately after the kmalloc path fails.
> Therefore, using kzalloc() is sufficient in this case.
>
> Fixes: 41b3caa7c076 ("neighbour: Add hlist_node to struct neighbour")
This commit followed the old hash_buckets allocation, so I'd add
Fixes: ab101c553bc1 ("neighbour: use kvzalloc()/kvfree()")
too.
Both commits were introduced in v6.13, so there's no difference in terms
of backporting though.
Also, it would be nice to CC mm maintainers in case they have some
comments.
> Signed-off-by: Kohei Enju <enjuk@amazon.com>
> ---
> net/core/neighbour.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/net/core/neighbour.c b/net/core/neighbour.c
> index d8dd686b5287..344c9cd168ec 100644
> --- a/net/core/neighbour.c
> +++ b/net/core/neighbour.c
> @@ -518,7 +518,7 @@ static struct neigh_hash_table *neigh_hash_alloc(unsigned int shift)
> if (!ret)
> return NULL;
>
> - hash_heads = kvzalloc(size, GFP_ATOMIC);
> + hash_heads = kzalloc(size, GFP_ATOMIC);
> if (!hash_heads) {
> kfree(ret);
> return NULL;
> @@ -536,7 +536,7 @@ static void neigh_hash_free_rcu(struct rcu_head *head)
> struct neigh_hash_table,
> rcu);
>
> - kvfree(nht->hash_heads);
> + kfree(nht->hash_heads);
> kfree(nht);
> }
>
> --
> 2.39.5 (Apple Git-154)
next prev parent reply other threads:[~2025-02-16 19:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-16 16:30 [PATCH net-next v1] neighbour: Replace kvzalloc() with kzalloc() when GFP_ATOMIC is specified Kohei Enju
2025-02-16 19:06 ` Kuniyuki Iwashima [this message]
2025-02-17 8:56 ` Eric Dumazet
2025-02-17 16:52 ` Kohei Enju
2025-02-17 18:43 ` Vlastimil Babka
2025-02-18 4:22 ` Kohei Enju
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=20250216190642.31169-1-kuniyu@amazon.com \
--to=kuniyu@amazon.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=enjuk@amazon.com \
--cc=gnaaman@drivenets.com \
--cc=horms@kernel.org \
--cc=joel.granados@kernel.org \
--cc=kohei.enju@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizetao1@huawei.com \
--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