From: Purva Yeshi <purvayeshi550@gmail.com>
To: Kuniyuki Iwashima <kuniyu@amazon.com>
Cc: davem@davemloft.net, dsahern@kernel.org, edumazet@google.com,
horms@kernel.org, kuba@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com
Subject: Re: [PATCH] net: ipv4: Fix uninitialized pointer warning in fnhe_remove_oldest
Date: Fri, 18 Apr 2025 15:01:52 +0530 [thread overview]
Message-ID: <43d2438f-2fea-45d9-a49e-e03a5cdc6800@gmail.com> (raw)
In-Reply-To: <20250417220022.23265-1-kuniyu@amazon.com>
On 18/04/25 03:30, Kuniyuki Iwashima wrote:
> From: Purva Yeshi <purvayeshi550@gmail.com>
> Date: Thu, 17 Apr 2025 15:11:26 +0530
>> Fix Smatch-detected issue:
>> net/ipv4/route.c:605 fnhe_remove_oldest() error:
>> uninitialized symbol 'oldest_p'.
>>
>> Initialize oldest_p to NULL to avoid uninitialized pointer warning in
>> fnhe_remove_oldest.
>
> How does it remain uninitialised ?
>
> update_or_create_fnhe() ensures the bucket is not empty before
> calling fnhe_remove_oldest().
Hi Kuniyuki,
Thanks for the feedback.
Smatch reports this because oldest_p is conditionally assigned inside
the loop, and it doesn't reason about the guarantees made by
update_or_create_fnhe() (i.e., that the list is non-empty). So it flags
oldest_p as potentially uninitialized when dereferenced.
I understand your point, logically, the code is safe, and the warning is
a false positive.
>
>
>>
>> Check that oldest_p is not NULL after the loop to ensure no dereferencing
>> of uninitialized pointers.
>>
>> Signed-off-by: Purva Yeshi <purvayeshi550@gmail.com>
>> ---
>> net/ipv4/route.c | 11 +++++++----
>> 1 file changed, 7 insertions(+), 4 deletions(-)
>>
>> diff --git a/net/ipv4/route.c b/net/ipv4/route.c
>> index 753704f75b2c..2e5159127cb9 100644
>> --- a/net/ipv4/route.c
>> +++ b/net/ipv4/route.c
>> @@ -587,7 +587,7 @@ static void fnhe_flush_routes(struct fib_nh_exception *fnhe)
>>
>> static void fnhe_remove_oldest(struct fnhe_hash_bucket *hash)
>> {
>> - struct fib_nh_exception __rcu **fnhe_p, **oldest_p;
>> + struct fib_nh_exception __rcu **fnhe_p, **oldest_p = NULL;
>> struct fib_nh_exception *fnhe, *oldest = NULL;
>>
>> for (fnhe_p = &hash->chain; ; fnhe_p = &fnhe->fnhe_next) {
>> @@ -601,9 +601,12 @@ static void fnhe_remove_oldest(struct fnhe_hash_bucket *hash)
>> oldest_p = fnhe_p;
>> }
>> }
>> - fnhe_flush_routes(oldest);
>> - *oldest_p = oldest->fnhe_next;
>> - kfree_rcu(oldest, rcu);
>> +
>> + if (oldest_p) { /* Ensure to have valid oldest_p element */
>> + fnhe_flush_routes(oldest);
>> + *oldest_p = oldest->fnhe_next;
>> + kfree_rcu(oldest, rcu);
>> + }
>> }
>>
>> static u32 fnhe_hashfun(__be32 daddr)
>> --
prev parent reply other threads:[~2025-04-18 9:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 9:41 [PATCH] net: ipv4: Fix uninitialized pointer warning in fnhe_remove_oldest Purva Yeshi
2025-04-17 22:00 ` Kuniyuki Iwashima
2025-04-18 5:03 ` David Ahern
2025-04-18 9:46 ` Purva Yeshi
2025-04-18 9:31 ` Purva Yeshi [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=43d2438f-2fea-45d9-a49e-e03a5cdc6800@gmail.com \
--to=purvayeshi550@gmail.com \
--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-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;
as well as URLs for NNTP newsgroup(s).