| 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
| ||
|
Message-Id: <164697301313.12732.14395145202660656158.git-patchwork-notify@kernel.org>
Date: Fri, 11 Mar 2022 04:30:13 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Ilya Maximets <i.maximets@....org>
Cc: kuba@...nel.org, roid@...dia.com, davem@...emloft.net,
pshelar@....org, cpp.code.lv@...il.com, netdev@...r.kernel.org,
dev@...nvswitch.org, linux-kernel@...r.kernel.org,
johannes@...solutions.net, aconole@...hat.com
Subject: Re: [PATCH net-next v2] net: openvswitch: fix uAPI incompatibility with
existing user space
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@...nel.org>:
On Wed, 9 Mar 2022 23:20:33 +0100 you wrote:
> Few years ago OVS user space made a strange choice in the commit [1]
> to define types only valid for the user space inside the copy of a
> kernel uAPI header. '#ifndef __KERNEL__' and another attribute was
> added later.
>
> This leads to the inevitable clash between user space and kernel types
> when the kernel uAPI is extended. The issue was unveiled with the
> addition of a new type for IPv6 extension header in kernel uAPI.
>
> [...]
Here is the summary with links:
- [net-next,v2] net: openvswitch: fix uAPI incompatibility with existing user space
https://git.kernel.org/netdev/net-next/c/1926407a4ab0
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