[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <153779150602.28003.4692837431529288988.stgit@warthog.procyon.org.uk>
Date: Mon, 24 Sep 2018 13:18:26 +0100
From: David Howells <dhowells@...hat.com>
To: jmorris@...ei.org
Cc: Randy Dunlap <rdunlap@...radead.org>,
"Serge E. Hallyn" <serge@...lyn.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
stable@...r.kernel.org, stable@...r.kernel.org,
Mat Martineau <mathew.j.martineau@...ux.intel.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Stephan Mueller <smueller@...onox.de>,
Lubomir Rintel <lkundrak@...sk>, dhowells@...hat.com,
keyrings@...r.kernel.org, linux-security-module@...r.kernel.org,
lkundrak@...sk, rdunlap@...radead.org, linux-kernel@...r.kernel.org
Subject: [PATCH 0/2] KEYS: Revert and replace incorrect UAPI fix
Hi James,
Here's a pair of fixes that need to go upstream asap, please:
(1) Revert an incorrect fix to the keyrings UAPI for a C++ reserved word
used as a struct member name. This change being reverted breaks
existing userspace code and is thus incorrect.
Further, *neither* name is consistent with the one in the keyutils
package public header.
(2) Fix the problem by using a union to make the name from keyutils
available in parallel and make the 'private' name unavailable in C++
with cpp-conditionals.
David
---
David Howells (1):
keys: Fix the use of the C++ keyword "private" in uapi/linux/keyctl.h
Lubomir Rintel (1):
Revert "uapi/linux/keyctl.h: don't use C++ reserved keyword as a struct member name"
include/uapi/linux/keyctl.h | 7 ++++++-
security/keys/dh.c | 2 +-
2 files changed, 7 insertions(+), 2 deletions(-)
Powered by blists - more mailing lists