From: <Ajay.Kathat@microchip.com>
To: <kvalo@kernel.org>, <lkp@intel.com>
Cc: <oe-kbuild-all@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
<linux-wireless@vger.kernel.org>
Subject: Re: drivers/net/wireless/microchip/wilc1000/cfg80211.c:361:42: sparse: sparse: incorrect type in assignment (different base types)
Date: Wed, 30 Aug 2023 00:34:23 +0000 [thread overview]
Message-ID: <cf141543-fff5-635c-ff51-22f1d9120e09@microchip.com> (raw)
In-Reply-To: <87a5uatfl1.fsf@kernel.org>
Hi Kalle,
On 8/29/23 01:31, Kalle Valo wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> Kalle Valo <kvalo@kernel.org> writes:
>
>> kernel test robot <lkp@intel.com> writes:
>>
>>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>>> head: 727dbda16b83600379061c4ca8270ef3e2f51922
>>> commit: c5b331d4f550fb78bf1a553b2517616a5ea913d6 wifi: wilc1000: add WPA3 SAE support
>>> date: 1 year, 3 months ago
>>> config: i386-randconfig-063-20230829 (https://download.01.org/0day-ci/archive/20230829/202308290615.lUTIgqUl-lkp@intel.com/config)
>>> compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
>>> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230829/202308290615.lUTIgqUl-lkp@intel.com/reproduce)
>>>
>>> If you fix the issue in a separate patch/commit (i.e. not just a new version of
>>> the same patch/commit), kindly add following tags
>>> | Reported-by: kernel test robot <lkp@intel.com>
>>> | Closes: https://lore.kernel.org/oe-kbuild-all/202308290615.lUTIgqUl-lkp@intel.com/
>>>
>>> sparse warnings: (new ones prefixed by >>)
>>>>> drivers/net/wireless/microchip/wilc1000/cfg80211.c:361:42: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned int key_mgmt_suite @@ got restricted __be32 [usertype] @@
>>> drivers/net/wireless/microchip/wilc1000/cfg80211.c:361:42: sparse: expected unsigned int key_mgmt_suite
>>> drivers/net/wireless/microchip/wilc1000/cfg80211.c:361:42: sparse: got restricted __be32 [usertype]
>>
>> Yeah, this is an old issue but we really should try to fix this,
>> especially so as I would like to make wireless code sparse warning free
>> in the near future. IIRC there were some problems with nl80211 interface
>> as well so this might not be simple fix still.
>
> For reference here's the old discussion:
>
> https://patchwork.kernel.org/project/linux-wireless/patch/20220720160302.231516-1-ajay.kathat@microchip.com/
>
> Any volunteers to help fix this? I would prefers fixes for issues like
> this compared to questionable random cleanups we always get.
>
> Maybe we should come up with a todo list somewhere and advocate the
> "cleaners" to work on those items instead?
>
It seems, the wpa_s is modified to handle the byte order for
'key_mgmt_suite' value. The changes are committed in [1] and it should
work for any byte order.
Now, the above sparse warning can be fixed by just removing the byte
conversion before passing to wpa_s.
vif->auth.key_mgmt_suite = cpu_to_be32(sme->crypto.akm_suites[0]);
to
vif->auth.key_mgmt_suite = sme->crypto.akm_suites[0];
I can push a patch to fix the sparse warning. However the patch will
work with updated wpa_s.
1.
https://w1.fi/cgit/hostap/commit/?id=8392ea9e75eacf30cb09671e463d9a37c3eadd6a
next prev parent reply other threads:[~2023-08-30 0:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 22:56 kernel test robot
2023-08-29 6:09 ` Kalle Valo
2023-08-29 8:31 ` Kalle Valo
2023-08-30 0:34 ` Ajay.Kathat [this message]
2024-02-14 8:42 ` Alexis Lothoré
2024-02-14 9:29 ` Johannes Berg
2024-02-14 11:03 ` Alexis Lothoré
2024-02-14 11:28 ` Johannes Berg
2024-02-15 4:10 ` Ajay.Kathat
-- strict thread matches above, loose matches on Subject: below --
2023-11-05 8:00 kernel test robot
2023-10-05 13:11 kernel test robot
2023-04-26 19:15 kernel test robot
2023-01-22 8:12 kernel test robot
2023-01-12 16:05 kernel test robot
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=cf141543-fff5-635c-ff51-22f1d9120e09@microchip.com \
--to=ajay.kathat@microchip.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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®