From: David Laight <David.Laight@ACULAB.COM>
To: 'Arnd Bergmann' <arnd@kernel.org>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
"Martyna Szapar-Mudlaw" <martyna.szapar-mudlaw@linux.intel.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Marcin Szycik <marcin.szycik@linux.intel.com>,
Amritha Nambiar <amritha.nambiar@intel.com>,
Michal Swiatkowski <michal.swiatkowski@linux.intel.com>,
Wojciech Drewek <wojciech.drewek@intel.com>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] ethernet: ice: avoid gcc-9 integer overflow warning
Date: Wed, 15 Feb 2023 10:58:46 +0000 [thread overview]
Message-ID: <abc3ba4b46f942d595b6c5fa164bc4f8@AcuMS.aculab.com> (raw)
In-Reply-To: <20230214132002.1498163-1-arnd@kernel.org>
From: Arnd Bergmann
> Sent: 14 February 2023 13:20
>
> From: Arnd Bergmann <arnd@arndb.de>
>
> With older compilers like gcc-9, the calculation of the vlan
> priority field causes a warning from the byteswap:
>
...
>
> Fixes: 34800178b302 ("ice: Add support for VLAN priority filters in switchdev")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> drivers/net/ethernet/intel/ice/ice_tc_lib.c | 10 ++++------
> 1 file changed, 4 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/net/ethernet/intel/ice/ice_tc_lib.c b/drivers/net/ethernet/intel/ice/ice_tc_lib.c
> index 6b48cbc049c6..e9932446185c 100644
> --- a/drivers/net/ethernet/intel/ice/ice_tc_lib.c
> +++ b/drivers/net/ethernet/intel/ice/ice_tc_lib.c
> @@ -1453,10 +1453,9 @@ ice_parse_cls_flower(struct net_device *filter_dev, struct ice_vsi *vsi,
> }
>
> if (match.mask->vlan_priority) {
> + u16 prio = (match.key->vlan_priority << VLAN_PRIO_SHIFT) & VLAN_PRIO_MASK;
> fltr->flags |= ICE_TC_FLWR_FIELD_VLAN_PRIO;
> - headers->vlan_hdr.vlan_prio =
> - cpu_to_be16((match.key->vlan_priority <<
> - VLAN_PRIO_SHIFT) & VLAN_PRIO_MASK);
> + headers->vlan_hdr.vlan_prio = cpu_to_be16(prio);
> }
Is there something that will do:
unsigned int pri = match.key->vlan_priority & (VLAN_PRIO_MASK >> VLAN_PRIO_SHIFT);
headers->vlan_hdr.vlan_prio = pri << (VLAN_PRIO_SHIFT ^ (le ? 8 : 0));
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
prev parent reply other threads:[~2023-02-15 10:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 13:19 [PATCH] ethernet: ice: avoid gcc-9 integer overflow warning Arnd Bergmann
2023-02-14 14:19 ` [Intel-wired-lan] " Alexander Lobakin
2023-02-14 15:40 ` Maciej Fijalkowski
2023-02-15 10:58 ` David Laight [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=abc3ba4b46f942d595b6c5fa164bc4f8@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=amritha.nambiar@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin.szycik@linux.intel.com \
--cc=martyna.szapar-mudlaw@linux.intel.com \
--cc=michal.swiatkowski@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wojciech.drewek@intel.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