From: Stephen Hemminger <stephen@networkplumber.org>
To: Anatoly Burakov <anatoly.burakov@intel.com>,
Vladimir Medvedkin <vladimir.medvedkin@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: warnings in e1000 with gcc-16
Date: Fri, 14 Nov 2025 09:07:59 -0800 [thread overview]
Message-ID: <20251114090759.14792716@phoenix> (raw)
Building with latest gcc-16 and DPDK shows these new warnings.
With current annotations on rte_malloc, compiler is now tracking sizes.
../drivers/net/intel/e1000/igb_ethdev.c: In function ‘eth_igb_add_del_flex_filter’:
../drivers/net/intel/e1000/igb_ethdev.c:4280:50: warning: writing 64 bytes into a region of size 24 [-Wstringop-overflow=]
4280 | flex_filter->filter_info.mask[i] = mask;
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~
../drivers/net/intel/e1000/igb_ethdev.c:4265:23: note: at offset 152 into destination object of size 176 allocated by ‘rte_zmalloc’
4265 | flex_filter = rte_zmalloc("e1000_flex_filter",
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
4266 | sizeof(struct e1000_flex_filter), 0);
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../drivers/net/intel/e1000/igb_ethdev.c:4280:50: warning: writing 64 bytes into a region of size 0 [-Wstringop-overflow=]
4280 | flex_filter->filter_info.mask[i] = mask;
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~
../drivers/net/intel/e1000/igb_ethdev.c:4265:23: note: at offset 216 into destination object of size 176 allocated by ‘rte_zmalloc’
4265 | flex_filter = rte_zmalloc("e1000_flex_filter",
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
4266 | sizeof(struct e1000_flex_filter), 0);
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../drivers/net/intel/e1000/igb_ethdev.c:4280:50: warning: writing 64 bytes into a region of size 0 [-Wstringop-overflow=]
4280 | flex_filter->filter_info.mask[i] = mask;
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~
../drivers/net/intel/e1000/igb_ethdev.c:4265:23: note: at offset 280 into destination object of size 176 allocated by ‘rte_zmalloc’
4265 | flex_filter = rte_zmalloc("e1000_flex_filter",
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
4266 | sizeof(struct e1000_flex_filter), 0);
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
reply other threads:[~2025-11-14 17:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20251114090759.14792716@phoenix \
--to=stephen@networkplumber.org \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=vladimir.medvedkin@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 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.