From: Pavel Machek <pavel@denx.de>
To: Sasha Levin <sashal@kernel.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org, "GONG,
Ruiqi" <gongruiqi1@huawei.com>,
GONG@vger.kernel.org,
"Gustavo A . R . Silva" <gustavoars@kernel.org>,
Kees Cook <keescook@chromium.org>,
Florian Westphal <fw@strlen.de>,
pablo@netfilter.org, kadlec@netfilter.org, roopa@nvidia.com,
razor@blackwall.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
bridge@lists.linux-foundation.org, netdev@vger.kernel.org
Subject: Re: [PATCH AUTOSEL 4.14 6/8] netfilter: ebtables: fix fortify warnings in size_entry_mwt()
Date: Mon, 11 Sep 2023 11:36:15 +0200 [thread overview]
Message-ID: <ZP7fj1LW3YLu2LrM@duo.ucw.cz> (raw)
In-Reply-To: <20230908182127.3461199-6-sashal@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 886 bytes --]
Hi!
> [ Upstream commit a7ed3465daa240bdf01a5420f64336fee879c09d ]
>
> When compiling with gcc 13 and CONFIG_FORTIFY_SOURCE=y, the following
> warning appears:
>
> In function ‘fortify_memcpy_chk’,
> inlined from ‘size_entry_mwt’ at net/bridge/netfilter/ebtables.c:2118:2:
> ./include/linux/fortify-string.h:592:25: error: call to ‘__read_overflow2_field’
> declared with attribute warning: detected read beyond size of field (2nd parameter);
> maybe use struct_group()? [-Werror=attribute-warning]
> 592 | __read_overflow2_field(q_size_field, size);
> |
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This is not queued for 4.19. Mistake?
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2023-09-11 22:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 18:21 [PATCH AUTOSEL 4.14 1/8] wifi: ath9k: fix printk specifier Sasha Levin
2023-09-08 18:21 ` [PATCH AUTOSEL 4.14 2/8] wifi: mwifiex: fix fortify warning Sasha Levin
2023-09-08 18:21 ` [PATCH AUTOSEL 4.14 3/8] crypto: lib/mpi - avoid null pointer deref in mpi_cmp_ui() Sasha Levin
2023-09-08 18:21 ` [PATCH AUTOSEL 4.14 4/8] tpm_tis: Resend command to recover from data transfer errors Sasha Levin
2023-09-08 18:21 ` [PATCH AUTOSEL 4.14 5/8] alx: fix OOB-read compiler warning Sasha Levin
2023-09-08 18:21 ` [PATCH AUTOSEL 4.14 6/8] netfilter: ebtables: fix fortify warnings in size_entry_mwt() Sasha Levin
2023-09-11 9:36 ` Pavel Machek [this message]
2023-09-08 18:21 ` [PATCH AUTOSEL 4.14 7/8] wifi: cfg80211: ocb: don't leave if not joined Sasha Levin
2023-09-11 9:38 ` Pavel Machek
2023-09-08 18:21 ` [PATCH AUTOSEL 4.14 8/8] Bluetooth: btusb: Fix quirks table naming Sasha Levin
2023-09-11 9:40 ` Pavel Machek
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=ZP7fj1LW3YLu2LrM@duo.ucw.cz \
--to=pavel@denx.de \
--cc=GONG@vger.kernel.org \
--cc=bridge@lists.linux-foundation.org \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=gongruiqi1@huawei.com \
--cc=gustavoars@kernel.org \
--cc=kadlec@netfilter.org \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
/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