public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Lobakin <alexandr.lobakin@intel.com>
To: Arnd Bergmann <arnd@kernel.org>
Cc: "Johannes Berg" <johannes@sipsolutions.net>,
	"David S. Miller" <davem@davemloft.net>,
	"Eric Dumazet" <edumazet@google.com>,
	"Jakub Kicinski" <kuba@kernel.org>,
	"Paolo Abeni" <pabeni@redhat.com>,
	"Arnd Bergmann" <arnd@arndb.de>, "Felix Fietkau" <nbd@nbd.name>,
	"Alexander Wetzel" <alexander@wetzel-home.de>,
	"Toke Høiland-Jørgensen" <toke@toke.dk>,
	"Andrei Otcheretianski" <andrei.otcheretianski@intel.com>,
	linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] wifi: mac80211: avoid u32_encode_bits() warning
Date: Tue, 14 Feb 2023 18:21:47 +0100	[thread overview]
Message-ID: <1c1439f4-b5d5-ba59-97a7-e2edeb879fa3@intel.com> (raw)
In-Reply-To: <20230214132025.1532147-1-arnd@kernel.org>

From: Arnd Bergmann <arnd@kernel.org>
Date: Tue, 14 Feb 2023 14:20:21 +0100

> From: Arnd Bergmann <arnd@arndb.de>
> 
> gcc-9 triggers a false-postive warning in ieee80211_mlo_multicast_tx()
> for u32_encode_bits(ffs(links) - 1, ...), since ffs() can return zero
> on an empty bitmask, and the negative argument to u32_encode_bits()
> is then out of range:
> 
> In file included from include/linux/ieee80211.h:21,
>                  from include/net/cfg80211.h:23,
>                  from net/mac80211/tx.c:23:
> In function 'u32_encode_bits',
>     inlined from 'ieee80211_mlo_multicast_tx' at net/mac80211/tx.c:4437:17,
>     inlined from 'ieee80211_subif_start_xmit' at net/mac80211/tx.c:4485:3:
> include/linux/bitfield.h:177:3: error: call to '__field_overflow' declared with attribute error: value doesn't fit into mask
>   177 |   __field_overflow();     \
>       |   ^~~~~~~~~~~~~~~~~~
> include/linux/bitfield.h:197:2: note: in expansion of macro '____MAKE_OP'
>   197 |  ____MAKE_OP(u##size,u##size,,)
>       |  ^~~~~~~~~~~
> include/linux/bitfield.h:200:1: note: in expansion of macro '__MAKE_OP'
>   200 | __MAKE_OP(32)
>       | ^~~~~~~~~
> 
> Newer compiler versions do not cause problems with the zero argument
> because they do not consider this a __builtin_constant_p().
> It's also harmless since the hweight16() check already guarantees
> that this cannot be 0.
> 
> Replace the ffs() with an equivalent find_first_bit() check that
> matches the later for_each_set_bit() style and avoids the warning.
> 
> Fixes: 963d0e8d08d9 ("wifi: mac80211: optionally implement MLO multicast TX")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
>  net/mac80211/tx.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/net/mac80211/tx.c b/net/mac80211/tx.c
> index defe97a31724..118648af979c 100644
> --- a/net/mac80211/tx.c
> +++ b/net/mac80211/tx.c
> @@ -4434,7 +4434,7 @@ static void ieee80211_mlo_multicast_tx(struct net_device *dev,
>  	u32 ctrl_flags = IEEE80211_TX_CTRL_MCAST_MLO_FIRST_TX;
>  
>  	if (hweight16(links) == 1) {
> -		ctrl_flags |= u32_encode_bits(ffs(links) - 1,
> +		ctrl_flags |= u32_encode_bits(find_first_bit(&links, 16) - 1,

Uff, IIRC find_first_bit() matches __ffs() calling convention, not ffs()
one. They're off-by-one from each other, which means you need to drop
this `- 1`.
As this branch happens only when hweight is 1 => @links has a bit set,
it's safe to just use __ffs() here directly, but up to you.
find_first_bit() is fine, too, since it will be optimized out to __ffs()
at the end in this case.

>  					      IEEE80211_TX_CTRL_MLO_LINK);
>  
>  		__ieee80211_subif_start_xmit(skb, sdata->dev, 0, ctrl_flags,
Thanks,
Olek

      reply	other threads:[~2023-02-14 17:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-14 13:20 [PATCH] wifi: mac80211: avoid u32_encode_bits() warning Arnd Bergmann
2023-02-14 17:21 ` Alexander Lobakin [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=1c1439f4-b5d5-ba59-97a7-e2edeb879fa3@intel.com \
    --to=alexandr.lobakin@intel.com \
    --cc=alexander@wetzel-home.de \
    --cc=andrei.otcheretianski@intel.com \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=johannes@sipsolutions.net \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nbd@nbd.name \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=toke@toke.dk \
    /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