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
| ||
|
Date: Fri, 9 Oct 2020 09:21:41 +0200 From: Greg KH <gregkh@...uxfoundation.org> To: Pavel Machek <pavel@...x.de> Cc: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>, x86@...nel.org, linux-sgx@...r.kernel.org, linux-kernel@...r.kernel.org, linux-security-module@...r.kernel.org, linux-mm@...ck.org, Andrew Morton <akpm@...ux-foundation.org>, Matthew Wilcox <willy@...radead.org>, Jethro Beekman <jethro@...tanix.com>, Haitao Huang <haitao.huang@...ux.intel.com>, Chunyang Hui <sanqian.hcy@...fin.com>, Jordan Hand <jorhand@...ux.microsoft.com>, Nathaniel McCallum <npmccallum@...hat.com>, Seth Moore <sethmo@...gle.com>, Darren Kenny <darren.kenny@...cle.com>, Sean Christopherson <sean.j.christopherson@...el.com>, Suresh Siddha <suresh.b.siddha@...el.com>, andriy.shevchenko@...ux.intel.com, asapek@...gle.com, bp@...en8.de, cedric.xing@...el.com, chenalexchen@...gle.com, conradparker@...gle.com, cyhanish@...gle.com, dave.hansen@...el.com, haitao.huang@...el.com, kai.huang@...el.com, kai.svahn@...el.com, kmoy@...gle.com, ludloff@...gle.com, luto@...nel.org, nhorman@...hat.com, puiterwijk@...hat.com, rientjes@...gle.com, tglx@...utronix.de, yaozhangx@...gle.com, mikko.ylinen@...el.com Subject: Re: [PATCH v39 11/24] x86/sgx: Add SGX enclave driver On Fri, Oct 09, 2020 at 09:10:45AM +0200, Pavel Machek wrote: > Hi! > > > > new file mode 100644 > > > index 000000000000..f54da5f19c2b > > > --- /dev/null > > > +++ b/arch/x86/kernel/cpu/sgx/driver.c > > > @@ -0,0 +1,173 @@ > > > +// SPDX-License-Identifier: (GPL-2.0 OR BSD-3-Clause) > > > > You use gpl-only header files in this file, so how in the world can it > > be bsd-3 licensed? > > > > Please get your legal department to agree with this, after you explain > > to them how you are mixing gpl2-only code in with this file. > > This specifies license of driver.c, not of the headers included. Are > you saying that it is impossible to have a kernel driver with anything > else than GPL-2? That would be news to many, and that's not what > current consensus is. If you want to write any non-GPL-2-only kernel code, you had better be consulting your lawyers and get very explicit instructions on how to do this in a way that does not violate any licenses. I am not a lawyer, and will not be giving you any such advice, as I think it's not something that people should be doing. greg k-h
Powered by blists - more mailing lists