From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, elder@kernel.org
Subject: Re: [PATCH net-next] net: ipa: don't proceed to out-of-bound write
Date: Fri, 20 May 2022 01:50:13 +0000 [thread overview]
Message-ID: <165301141326.6731.4497591034558946002.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220519004417.2109886-1-kuba@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 18 May 2022 17:44:17 -0700 you wrote:
> GCC 12 seems upset that we check ipa_irq against array bound
> but then proceed, anyway:
>
> drivers/net/ipa/ipa_interrupt.c: In function ‘ipa_interrupt_add’:
> drivers/net/ipa/ipa_interrupt.c:196:27: warning: array subscript 30 is above array bounds of ‘void (*[30])(struct ipa *, enum ipa_irq_id)’ [-Warray-bounds]
> 196 | interrupt->handler[ipa_irq] = handler;
> | ~~~~~~~~~~~~~~~~~~^~~~~~~~~
> drivers/net/ipa/ipa_interrupt.c:42:27: note: while referencing ‘handler’
> 42 | ipa_irq_handler_t handler[IPA_IRQ_COUNT];
> | ^~~~~~~
>
> [...]
Here is the summary with links:
- [net-next] net: ipa: don't proceed to out-of-bound write
https://git.kernel.org/netdev/net-next/c/1172aa6e4a19
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-05-20 1:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 0:44 [PATCH net-next] net: ipa: don't proceed to out-of-bound write Jakub Kicinski
2022-05-19 1:22 ` Alex Elder
2022-05-20 1:50 ` patchwork-bot+netdevbpf [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=165301141326.6731.4497591034558946002.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=elder@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).