netdev - Re: [PATCH net-next] bnx2x: Set ivi->vlan field as an integer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: 
 <172386302825.3683187.17491130875681163118.git-patchwork-notify@kernel.org>
Date: Sat, 17 Aug 2024 02:50:28 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Simon Horman <horms@...nel.org>
Cc: skalluru@...vell.com, manishc@...vell.com, davem@...emloft.net,
 edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
 netdev@...r.kernel.org
Subject: Re: [PATCH net-next] bnx2x: Set ivi->vlan field as an integer

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:

On Thu, 15 Aug 2024 16:27:46 +0100 you wrote:
> In bnx2x_get_vf_config():
> * The vlan field of ivi is a 32-bit integer, it is used to store a vlan ID.
> * The vlan field of bulletin is a 16-bit integer, it is also used to store
>   a vlan ID.
> 
> In the current code, ivi->vlan is set using memset. But in the case of
> setting it to the value of bulletin->vlan, this involves reading
> 32 bits from a 16bit source. This is likely safe, as the following
> 6 bytes are padding in the same structure, but none the less, it seems
> undesirable.
> 
> [...]

Here is the summary with links:
  - [net-next] bnx2x: Set ivi->vlan field as an integer
    https://git.kernel.org/netdev/net-next/c/a99ef548bba0

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html