[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180910150903.249031442dd7fe43e01812cf@linux-foundation.org>
Date: Mon, 10 Sep 2018 15:09:03 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Eugene Syromiatnikov <esyr@...hat.com>
Cc: Randy Dunlap <rdunlap@...radead.org>,
LKML <linux-kernel@...r.kernel.org>,
David Howells <dhowells@...hat.com>,
James Morris <jmorris@...ei.org>,
"Serge E. Hallyn" <serge@...lyn.com>, keyrings@...r.kernel.org,
linux-security-module@...r.kernel.org,
Mat Martineau <mathew.j.martineau@...ux.intel.com>,
stable <stable@...r.kernel.org>
Subject: Re: [PATCH resend] uapi/linux/keyctl.h: don't use C++ reserved
keyword as a struct member name
On Mon, 10 Sep 2018 00:00:18 +0200 Eugene Syromiatnikov <esyr@...hat.com> wrote:
> On Tue, Aug 28, 2018 at 04:34:04PM -0700, Randy Dunlap wrote:
> > From: Randy Dunlap <rdunlap@...radead.org>
> >
> > Since this header is in "include/uapi/linux/", apparently people
> > want to use it in userspace programs -- even in C++ ones.
> > However, the header uses a C++ reserved keyword ("private"),
> > so change that to "dh_private" instead to allow the header file
> > to be used in C++ userspace.
>
> This change breaks all existing C programs that rely on <linux/keyctl.h>
> uapi header in order to get struct keyctl_dh_params definition, however.
Are there such programs? Do they reference the `private' field?
Powered by blists - more mailing lists