[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <165416821239.26072.8874912583921079305.git-patchwork-notify@kernel.org>
Date: Thu, 02 Jun 2022 11:10:12 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Alexander Lobakin <alexandr.lobakin@...el.com>
Cc: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, jesse.brandeburg@...el.com,
anthony.l.nguyen@...el.com, jeffrey.t.kirsher@...el.com,
anirudh.venkataramanan@...el.com, bruce.w.allan@...el.com,
maciej.fijalkowski@...el.com, michal.swiatkowski@...ux.intel.com,
wojciech.drewek@...el.com, marcin.szycik@...ux.intel.com,
martyna.szapar-mudlaw@...el.com, netdev@...r.kernel.org,
intel-wired-lan@...ts.osuosl.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net] ice: fix access-beyond-end in the switch code
Hello:
This patch was applied to netdev/net.git (master)
by Paolo Abeni <pabeni@...hat.com>:
On Wed, 1 Jun 2022 12:59:24 +0200 you wrote:
> Global `-Warray-bounds` enablement revealed some problems, one of
> which is the way we define and use AQC rules messages.
> In fact, they have a shared header, followed by the actual message,
> which can be of one of several different formats. So it is
> straightforward enough to define that header as a separate struct
> and then embed it into message structures as needed, but currently
> all the formats reside in one union coupled with the header. Then,
> the code allocates only the memory needed for a particular message
> format, leaving the union potentially incomplete.
> There are no actual reads or writes beyond the end of an allocated
> chunk, but at the same time, the whole implementation is fragile and
> backed by an equilibrium rather than strong type and memory checks.
>
> [...]
Here is the summary with links:
- [net] ice: fix access-beyond-end in the switch code
https://git.kernel.org/netdev/net/c/6e1ff618737a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists