From: patchwork-bot+netdevbpf@kernel•org
To: Gustavo A. R. Silva <gustavoars@kernel•org>
Cc: aelior@marvell•com, manishc@marvell•com, davem@davemloft•net,
edumazet@google•com, kuba@kernel•org, pabeni@redhat•com,
Michal.Kalderon@cavium•com, netdev@vger•kernel.org,
linux-kernel@vger•kernel.org, linux-hardening@vger•kernel.org
Subject: Re: [PATCH] qed/red_ll2: Fix undefined behavior bug in struct qed_ll2_info
Date: Tue, 03 Oct 2023 08:40:26 +0000 [thread overview]
Message-ID: <169632242601.9748.14967908798498404874.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <ZQ+Nz8DfPg56pIzr@work>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat•com>:
On Sat, 23 Sep 2023 19:15:59 -0600 you wrote:
> The flexible structure (a structure that contains a flexible-array member
> at the end) `qed_ll2_tx_packet` is nested within the second layer of
> `struct qed_ll2_info`:
>
> struct qed_ll2_tx_packet {
> ...
> /* Flexible Array of bds_set determined by max_bds_per_packet */
> struct {
> struct core_tx_bd *txq_bd;
> dma_addr_t tx_frag;
> u16 frag_len;
> } bds_set[];
> };
>
> [...]
Here is the summary with links:
- qed/red_ll2: Fix undefined behavior bug in struct qed_ll2_info
https://git.kernel.org/netdev/net/c/eea03d18af9c
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:[~2023-10-03 8:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-24 1:15 [PATCH] qed/red_ll2: Fix undefined behavior bug in struct qed_ll2_info Gustavo A. R. Silva
2023-09-23 19:43 ` Kees Cook
2023-09-28 13:27 ` Simon Horman
2023-10-03 8:40 ` 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=169632242601.9748.14967908798498404874.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=Michal.Kalderon@cavium$(echo .)com \
--cc=aelior@marvell$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=gustavoars@kernel$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=linux-hardening@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=manishc@marvell$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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