Re: [PATCH net-next] genetlink: start to validate reserved header bytes

To: Jakub Kicinski <kuba@xxxxxxxxxx>
Subject: Re: [PATCH net-next] genetlink: start to validate reserved header bytes
Cc: davem@xxxxxxxxxxxxx, netdev@xxxxxxxxxxxxxxx, edumazet@xxxxxxxxxx, pabeni@xxxxxxxxxx, jiri@xxxxxxxxxxx, johannes@xxxxxxxxxxxxxxxx, linux-block@xxxxxxxxxxxxxxx, osmocom-net-gprs@xxxxxxxxxxxxxxxxx, linux-wpan@xxxxxxxxxxxxxxx, wireguard@xxxxxxxxxxxxxxx, linux-wireless@xxxxxxxxxxxxxxx, linux-scsi@xxxxxxxxxxxxxxx, target-devel@xxxxxxxxxxxxxxx, linux-pm@xxxxxxxxxxxxxxx, virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx, linux-cifs@xxxxxxxxxxxxxxx, cluster-devel@xxxxxxxxxx, mptcp@xxxxxxxxxxxxxxx, lvs-devel@xxxxxxxxxxxxxxx, netfilter-devel@xxxxxxxxxxxxxxx, linux-security-module@xxxxxxxxxxxxxxx, dev@xxxxxxxxxxxxxxx, linux-s390@xxxxxxxxxxxxxxx, tipc-discussion@xxxxxxxxxxxxxxxxxxxxx
From: patchwork-bot+netdevbpf@xxxxxxxxxx
Date: Mon, 29 Aug 2022 12:10:17 +0000

This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@xxxxxxxxxxxxx>:

On Wed, 24 Aug 2022 17:18:30 -0700 you wrote:
> We had historically not checked that genlmsghdr.reserved
> is 0 on input which prevents us from using those precious
> bytes in the future.
> One use case would be to extend the cmd field, which is
> currently just 8 bits wide and 256 is not a lot of commands
> for some core families.
> [...]

Here is the summary with links:
  - [net-next] genetlink: start to validate reserved header bytes

You are awesome, thank you!
Deet-doot-dot, I am a bot.

<Prev in Thread] Current Thread [Next in Thread>