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: <20190411154827.v2vkxlc2ecqkxyjv@treble> Date: Thu, 11 Apr 2019 10:48:27 -0500 From: Josh Poimboeuf <jpoimboe@...hat.com> To: Joe Lawrence <joe.lawrence@...hat.com> Cc: Masahiro Yamada <yamada.masahiro@...ionext.com>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, live-patching@...r.kernel.org, Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>, Jessica Yu <jeyu@...nel.org>, Jiri Kosina <jikos@...nel.org>, Joao Moreira <jmoreira@...e.de>, Konstantin Khlebnikov <khlebnikov@...dex-team.ru>, Michael Matz <matz@...e.de>, Miroslav Benes <mbenes@...e.cz>, Nicolai Stange <nstange@...e.de>, Petr Mladek <pmladek@...e.com> Subject: Re: [PATCH v3 1/9] livepatch: Create and include UAPI headers On Thu, Apr 11, 2019 at 10:30:45AM -0400, Joe Lawrence wrote: > On 4/10/19 8:32 PM, Masahiro Yamada wrote: > > On Thu, Apr 11, 2019 at 12:52 AM Joe Lawrence <joe.lawrence@...hat.com> wrote: > > > > > > From: Josh Poimboeuf <jpoimboe@...hat.com> > > > > > > Define klp prefixes in include/uapi/linux/livepatch.h, and use them for > > > replacing hard-coded values in kernel/livepatch/core.c. > > > > > > [ ... snip ... ] > >> > > > diff --git a/include/uapi/linux/livepatch.h b/include/uapi/linux/livepatch.h > > > new file mode 100644 > > > index 000000000000..bb86243de805 > > > --- /dev/null > > > +++ b/include/uapi/linux/livepatch.h > > > @@ -0,0 +1,17 @@ > > > +/* SPDX-License-Identifier: GPL-2.0 */ > > > > > > In my understanding, UAPI headers should be licensed under: > > > > /* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */ > > > > > > Good eye, that is an interesting licensing detail. Easy enough to update > assuming Josh (original author) is fine with adding the modifier. Sure. (and sorry, still behind on reviewing the rest of the changes...) -- Josh
Powered by blists - more mailing lists