From: "Coelho, Luciano" <luciano.coelho@intel.com>
To: "joe@perches.com" <joe@perches.com>,
"cgel.zte@gmail.com" <cgel.zte@gmail.com>
Cc: "zealci@zte.com.cn" <zealci@zte.com.cn>,
"kvalo@codeaurora.org" <kvalo@codeaurora.org>,
"Berg, Johannes" <johannes.berg@intel.com>,
"ye.guojin@zte.com.cn" <ye.guojin@zte.com.cn>,
"davem@davemloft.net" <davem@davemloft.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Korenblit, Miriam Rachel" <miriam.rachel.korenblit@intel.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"kuba@kernel.org" <kuba@kernel.org>
Subject: Re: [PATCH] iwlwifi: rs: fixup the return value type of iwl_legacy_rate_to_fw_idx()
Date: Wed, 17 Nov 2021 06:56:47 +0000 [thread overview]
Message-ID: <4ff3b088ef8b160dc2e878092c605e4481edb625.camel@intel.com> (raw)
In-Reply-To: <977fbfb8aaae8a54d8769f49d397d68f6387a0e8.camel@perches.com>
On Tue, 2021-11-16 at 22:41 -0800, Joe Perches wrote:
> On Wed, 2021-11-17 at 06:36 +0000, cgel.zte@gmail.com wrote:
> > From: Ye Guojin <ye.guojin@zte.com.cn>
> >
> > This was found by coccicheck:
> > ./drivers/net/wireless/intel/iwlwifi/fw/rs.c, 147, 10-21, WARNING
> > Unsigned expression compared with zero legacy_rate < 0
> []
> > diff --git a/drivers/net/wireless/intel/iwlwifi/fw/rs.c b/drivers/net/wireless/intel/iwlwifi/fw/rs.c
> []
> > @@ -142,7 +142,7 @@ u32 iwl_new_rate_from_v1(u32 rate_v1)
> > }
> > /* if legacy format */
> > } else {
> > - u32 legacy_rate = iwl_legacy_rate_to_fw_idx(rate_v1);
> > + int legacy_rate = iwl_legacy_rate_to_fw_idx(rate_v1);
> >
> > WARN_ON(legacy_rate < 0);
>
> Why not just remove the WARN_ON instead?
>
Well, iwl_legacy_rate_to_fw_idx() _tries_ to return -1 if we can't find
the index.
But there are a few more wrong things in this implementation:
1. the iwl_legacy_rate_to_fw_idx() function is only called inside the
fw/rs.c file, so it should be static;
2. if we don't find the idx and return -1, we WARN but still use the
value, which will cause the rate_v2 to be set to 0xffffffff, which I'm
pretty sure is not the intention.
So, this should be fixed properly, rather than just changing the
function to return int.
--
Cheers,
Luca.
prev parent reply other threads:[~2021-11-17 6:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 6:36 cgel.zte
2021-11-17 6:41 ` Joe Perches
2021-11-17 6:56 ` Coelho, Luciano [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=4ff3b088ef8b160dc2e878092c605e4481edb625.camel@intel.com \
--to=luciano.coelho@intel.com \
--cc=cgel.zte@gmail.com \
--cc=davem@davemloft.net \
--cc=joe@perches.com \
--cc=johannes.berg@intel.com \
--cc=kuba@kernel.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=miriam.rachel.korenblit@intel.com \
--cc=netdev@vger.kernel.org \
--cc=ye.guojin@zte.com.cn \
--cc=zealci@zte.com.cn \
/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
Powered by JetHome