From: Kees Cook <kees@kernel.org>
To: Kuniyuki Iwashima <kuniyu@amazon.com>, dsahern@kernel.org
Cc: davem@davemloft.net, edumazet@google.com, horms@kernel.org,
kuba@kernel.org, kuniyu@amazon.com,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com
Subject: Re: [PATCH] ipv4: fib: Fix fib_info_hash_alloc() allocation type
Date: Mon, 28 Apr 2025 20:52:59 -0700 [thread overview]
Message-ID: <89BC8935-21D1-45A9-AEA1-A4E52D193434@kernel.org> (raw)
In-Reply-To: <20250429004310.52559-1-kuniyu@amazon.com>
On April 28, 2025 5:43:05 PM PDT, Kuniyuki Iwashima <kuniyu@amazon.com> wrote:
>Thanks for CC me, David.
>
>From: David Ahern <dsahern@kernel.org>
>Date: Mon, 28 Apr 2025 16:50:53 -0600
>> On 4/25/25 11:05 PM, Kees Cook wrote:
>> > In preparation for making the kmalloc family of allocators type aware,
>> > we need to make sure that the returned type from the allocation matches
>> > the type of the variable being assigned. (Before, the allocator would
>> > always return "void *", which can be implicitly cast to any pointer type.)
>> >
>> > This was allocating many sizeof(struct hlist_head *) when it actually
>> > wanted sizeof(struct hlist_head). Luckily these are the same size.
>> > Adjust the allocation type to match the assignment.
>> >
>> > Signed-off-by: Kees Cook <kees@kernel.org>
>> > ---
>> > Cc: "David S. Miller" <davem@davemloft.net>
>> > Cc: David Ahern <dsahern@kernel.org>
>> > Cc: Eric Dumazet <edumazet@google.com>
>> > Cc: Jakub Kicinski <kuba@kernel.org>
>> > Cc: Paolo Abeni <pabeni@redhat.com>
>> > Cc: Simon Horman <horms@kernel.org>
>> > Cc: <netdev@vger.kernel.org>
>> > ---
>> > net/ipv4/fib_semantics.c | 2 +-
>> > 1 file changed, 1 insertion(+), 1 deletion(-)
>> >
>> > diff --git a/net/ipv4/fib_semantics.c b/net/ipv4/fib_semantics.c
>> > index f68bb9e34c34..37d12b0bc6be 100644
>> > --- a/net/ipv4/fib_semantics.c
>> > +++ b/net/ipv4/fib_semantics.c
>> > @@ -365,7 +365,7 @@ static struct hlist_head *fib_info_laddrhash_bucket(const struct net *net,
>> > static struct hlist_head *fib_info_hash_alloc(unsigned int hash_bits)
>> > {
>> > /* The second half is used for prefsrc */
>> > - return kvcalloc((1 << hash_bits) * 2, sizeof(struct hlist_head *),
>> > + return kvcalloc((1 << hash_bits) * 2, sizeof(struct hlist_head),
>> > GFP_KERNEL);
>> > }
>> >
>>
>> Reviewed-by: David Ahern <dsahern@kernel.org>
>>
>> Fixes: fa336adc100e ("ipv4: fib: Allocate fib_info_hash[] and
>> fib_info_laddrhash[] by kvcalloc().)
>
>I agree this should target net.git as the last statement
>will be false with LOCKDEP.
Which will be false with lockdep? Unless I'm missing it, I think hlist_head is always pointer sized:
struct hlist_head {
struct hlist_node *first;
};
>
>Reviewed-by: Kuniyuki Iwashima <kuniyu@amazon.com>
Thanks!
--
Kees Cook
next prev parent reply other threads:[~2025-04-29 3:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-26 6:05 Kees Cook
2025-04-28 20:01 ` Simon Horman
2025-04-28 22:50 ` David Ahern
2025-04-29 0:43 ` Kuniyuki Iwashima
2025-04-29 3:52 ` Kees Cook [this message]
2025-04-29 5:22 ` Kuniyuki Iwashima
2025-04-29 18:00 ` 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=89BC8935-21D1-45A9-AEA1-A4E52D193434@kernel.org \
--to=kees@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=linux-hardening@vger.kernel.org \
--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
all inboxes | Powered by JetHome®