All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Laight <David.Laight@ACULAB.COM>
To: 'Jakub Kicinski' <kuba@kernel.org>,
	"davem@davemloft.net" <davem@davemloft.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"edumazet@google.com" <edumazet@google.com>,
	"pabeni@redhat.com" <pabeni@redhat.com>,
	"jesse.brandeburg@intel.com" <jesse.brandeburg@intel.com>,
	"anthony.l.nguyen@intel.com" <anthony.l.nguyen@intel.com>
Subject: RE: [PATCH net-next] eth: ice: silence the GCC 12 array-bounds warning
Date: Fri, 20 May 2022 12:58:35 +0000	[thread overview]
Message-ID: <fbde22661c6b4d5f82ca47d5703ab7a8@AcuMS.aculab.com> (raw)
In-Reply-To: <20220520060906.2311308-1-kuba@kernel.org>

From: Jakub Kicinski
> Sent: 20 May 2022 07:09
> 
> GCC 12 gets upset because driver allocates partial
> struct ice_aqc_sw_rules_elem buffers. The writes are
> within bounds.
> 
> Silence these warnings for now, our build bot runs GCC 12
> so we won't allow any new instances.
> 
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> CC: jesse.brandeburg@intel.com
> CC: anthony.l.nguyen@intel.com
> ---
>  drivers/net/ethernet/intel/ice/Makefile | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/drivers/net/ethernet/intel/ice/Makefile b/drivers/net/ethernet/intel/ice/Makefile
> index 9183d480b70b..588b6e8c7920 100644
> --- a/drivers/net/ethernet/intel/ice/Makefile
> +++ b/drivers/net/ethernet/intel/ice/Makefile
> @@ -47,3 +47,8 @@ ice-$(CONFIG_DCB) += ice_dcb.o ice_dcb_nl.o ice_dcb_lib.o
>  ice-$(CONFIG_RFS_ACCEL) += ice_arfs.o
>  ice-$(CONFIG_XDP_SOCKETS) += ice_xsk.o
>  ice-$(CONFIG_ICE_SWITCHDEV) += ice_eswitch.o
> +
> +# FIXME: temporarily silence -Warray-bounds on non W=1 builds
> +ifndef KBUILD_EXTRA_WARN
> +CFLAGS_ice_switch.o += $(call cc-disable-warning, array-bounds)
> +endif
> --
> 2.34.3

Is it possible to just add:

CFLAGS_ice_switch.o += $(disable-Warray-bounds)

and then ensure that disable-Warray-bounds is defined
(and expanded) by the time it is actually expanded?
This might be before or after the makefile is expanded.
But it would mean that the work is only done once.
I've an idea that 'call cc-disable-warning' is non-trivial.

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)


  reply	other threads:[~2022-05-20 12:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-20  6:09 [PATCH net-next] eth: ice: silence the GCC 12 array-bounds warning Jakub Kicinski
2022-05-20 12:58 ` David Laight [this message]
2022-05-20 16:50   ` Jakub Kicinski

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=fbde22661c6b4d5f82ca47d5703ab7a8@AcuMS.aculab.com \
    --to=david.laight@aculab.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.