From: David Ahern <dsahern@kernel.org>
To: Dan Carpenter <dan.carpenter@linaro.org>,
Ido Schimmel <idosch@nvidia.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Petr Machata <petrm@nvidia.com>,
Kees Cook <keescook@chromium.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH net] nexthop: fix uninitialized variable in nla_put_nh_group_stats()
Date: Sat, 16 Mar 2024 10:29:27 -0600 [thread overview]
Message-ID: <893d73c3-e449-49ad-b297-1acef5dae38e@kernel.org> (raw)
In-Reply-To: <b2578acd-9838-45b6-a50d-96a86171b20e@moroto.mountain>
On 3/16/24 3:46 AM, Dan Carpenter wrote:
> The nh_grp_hw_stats_update() function doesn't always set "hw_stats_used"
> so it could be used without being initialized. Set it to false.
>
> Fixes: 5072ae00aea4 ("net: nexthop: Expose nexthop group HW stats to user space")
> Signed-off-by: Dan Carpenter <dan.carpenter@linaro.org>
> ---
> net/ipv4/nexthop.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/ipv4/nexthop.c b/net/ipv4/nexthop.c
> index 74928a9d1aa4..c25bfdf4e25f 100644
> --- a/net/ipv4/nexthop.c
> +++ b/net/ipv4/nexthop.c
> @@ -824,8 +824,8 @@ static int nla_put_nh_group_stats(struct sk_buff *skb, struct nexthop *nh,
> u32 op_flags)
> {
> struct nh_group *nhg = rtnl_dereference(nh->nh_grp);
> + bool hw_stats_used = false;
> struct nlattr *nest;
> - bool hw_stats_used;
> int err;
> int i;
>
Reviewed-by: David Ahern <dsahern@kernel.org>
The flag could be moved under
`if (op_flags & NHA_OP_FLAG_DUMP_HW_STATS ...`
as well.
next prev parent reply other threads:[~2024-03-16 16:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-16 9:46 [PATCH net] nexthop: fix uninitialized variable in nla_put_nh_group_stats() Dan Carpenter
2024-03-16 16:29 ` David Ahern [this message]
2024-03-17 7:56 ` Ido Schimmel
2024-03-18 8:02 ` Jiri Pirko
2024-03-18 8:11 ` Dan Carpenter
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=893d73c3-e449-49ad-b297-1acef5dae38e@kernel.org \
--to=dsahern@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=keescook@chromium.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.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).