From: patchwork-bot+netdevbpf@kernel.org
To: Florian Westphal <fw@strlen.de>
Cc: netdev@vger.kernel.org, pabeni@redhat.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org,
netfilter-devel@vger.kernel.org, gongruiqi1@huawei.com,
GONG@breakpoint.cc, gustavoars@kernel.org, keescook@chromium.org
Subject: Re: [PATCH net-next 01/10] netfilter: ebtables: fix fortify warnings in size_entry_mwt()
Date: Wed, 23 Aug 2023 02:00:25 +0000 [thread overview]
Message-ID: <169275602552.4956.7525189385907152255.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230822154336.12888-2-fw@strlen.de>
Hello:
This series was applied to netdev/net-next.git (main)
by Florian Westphal <fw@strlen.de>:
On Tue, 22 Aug 2023 17:43:22 +0200 you wrote:
> From: "GONG, Ruiqi" <gongruiqi1@huawei.com>
>
> 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);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> [...]
Here is the summary with links:
- [net-next,01/10] netfilter: ebtables: fix fortify warnings in size_entry_mwt()
https://git.kernel.org/netdev/net-next/c/a7ed3465daa2
- [net-next,02/10] netfilter: ebtables: replace zero-length array members
https://git.kernel.org/netdev/net-next/c/a2f02c9920b2
- [net-next,03/10] netfilter: ipset: refactor deprecated strncpy
https://git.kernel.org/netdev/net-next/c/e53314034b23
- [net-next,04/10] netfilter: nf_tables: refactor deprecated strncpy
https://git.kernel.org/netdev/net-next/c/6cdd75a4a66b
- [net-next,05/10] netfilter: nf_tables: refactor deprecated strncpy
https://git.kernel.org/netdev/net-next/c/7457af8bf994
- [net-next,06/10] netfilter: nft_osf: refactor deprecated strncpy
https://git.kernel.org/netdev/net-next/c/6d87a4eae89e
- [net-next,07/10] netfilter: nft_meta: refactor deprecated strncpy
https://git.kernel.org/netdev/net-next/c/ad156c23d65c
- [net-next,08/10] netfilter: x_tables: refactor deprecated strncpy
https://git.kernel.org/netdev/net-next/c/06f7d3c3f82c
- [net-next,09/10] netfilter: xtables: refactor deprecated strncpy
https://git.kernel.org/netdev/net-next/c/aa222dd190d6
- [net-next,10/10] netfilter: nf_tables: allow loop termination for pending fatal signal
https://git.kernel.org/netdev/net-next/c/169384fbe851
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-08-23 2:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 15:43 [PATCH net-next 00/10] netfilter updates for net-next Florian Westphal
2023-08-22 15:43 ` [PATCH net-next 01/10] netfilter: ebtables: fix fortify warnings in size_entry_mwt() Florian Westphal
2023-08-23 2:00 ` patchwork-bot+netdevbpf [this message]
2023-08-22 15:43 ` [PATCH net-next 02/10] netfilter: ebtables: replace zero-length array members Florian Westphal
2023-08-22 15:43 ` [PATCH net-next 03/10] netfilter: ipset: refactor deprecated strncpy Florian Westphal
2023-08-22 15:43 ` [PATCH net-next 04/10] netfilter: nf_tables: " Florian Westphal
2023-08-22 15:43 ` [PATCH net-next 05/10] " Florian Westphal
2023-08-22 15:43 ` [PATCH net-next 06/10] netfilter: nft_osf: " Florian Westphal
2023-08-22 15:43 ` [PATCH net-next 07/10] netfilter: nft_meta: " Florian Westphal
2023-08-22 15:43 ` [PATCH net-next 08/10] netfilter: x_tables: " Florian Westphal
2023-08-22 15:43 ` [PATCH net-next 09/10] netfilter: xtables: " Florian Westphal
2023-08-22 15:43 ` [PATCH net-next 10/10] netfilter: nf_tables: allow loop termination for pending fatal signal Florian Westphal
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=169275602552.4956.7525189385907152255.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=GONG@breakpoint.cc \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=gongruiqi1@huawei.com \
--cc=gustavoars@kernel.org \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@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.