Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+net\-next\]\s+genetlink\:\s+start\s+to\s+validate\s+reserved\s+header\s+bytes\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+net\-next\]\s+genetlink\:\s+start\s+to\s+validate\s+reserved\s+header\s+bytes\s*$/: 4 ]

Total 4 documents matching your query.

1. Re: [PATCH net-next] genetlink: start to validate reserved header bytes (score: 1): Author: "Jason A. Donenfeld" <Jason@xxxxxxxxx>; Date: Mon, 29 Aug 2022 12:32:54 -0400; Hi Jakub, FWIW, I wouldn't object to just leaving this at zero. I don't know of any wireguard userspaces doing anything with the reserved header field. Jason; /html/lvs-devel/2022-08/msg00022.html (11,459 bytes)
2. Re: [PATCH net-next] genetlink: start to validate reserved header bytes (score: 1): Author: patchwork-bot+netdevbpf@xxxxxxxxxx; Date: Mon, 29 Aug 2022 12:10:17 +0000; Hello: This patch was applied to netdev/net-next.git (master) by David S. Miller <davem@xxxxxxxxxxxxx>: Here is the summary with links: - [net-next] genetlink: start to validate reserved header bytes; /html/lvs-devel/2022-08/msg00021.html (11,512 bytes)
3. Re: [PATCH net-next] genetlink: start to validate reserved header bytes (score: 1): Author: Paul Moore <paul@xxxxxxxxxxxxxx>; Date: Thu, 25 Aug 2022 15:21:52 -0400; Acked-by: Paul Moore <paul@xxxxxxxxxxxxxx> (NetLabel) -- paul-moore.com; /html/lvs-devel/2022-08/msg00015.html (14,647 bytes)
4. [PATCH net-next] genetlink: start to validate reserved header bytes (score: 1): Author: Jakub Kicinski <kuba@xxxxxxxxxx>; Date: Wed, 24 Aug 2022 17:18:30 -0700; 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 current; /html/lvs-devel/2022-08/msg00012.html (38,565 bytes)

Current List: 1 - 4
Page: [1]