linux-kernel - Re: [PATCH v12 00/18] Enable FSGSBASE instructions

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 26 May 2020 10:23:54 +0200 (CEST)
From:   Richard Weinberger <richard@....at>
To:     David Laight <David.Laight@...LAB.COM>
Cc:     Sasha Levin <sashal@...nel.org>, hpa <hpa@...or.com>,
        tglx <tglx@...utronix.de>, Don Porter <porter@...unc.edu>,
        Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>,
        Andi Kleen <ak@...ux.intel.com>,
        linux-kernel <linux-kernel@...r.kernel.org>, bp <bp@...en8.de>,
        Andy Lutomirski <luto@...nel.org>,
        Dave Hansen <dave.hansen@...el.com>,
        Tony Luck <tony.luck@...el.com>,
        Ravi V Shankar <ravi.v.shankar@...el.com>,
        chang seok bae <chang.seok.bae@...el.com>
Subject: Re: [PATCH v12 00/18] Enable FSGSBASE instructions

----- Ursprüngliche Mail -----
> Von: "David Laight" <David.Laight@...LAB.COM>
> An: "Richard Weinberger" <richard.weinberger@...il.com>, "Sasha Levin" <sashal@...nel.org>
> CC: "hpa" <hpa@...or.com>, "tglx" <tglx@...utronix.de>, "Don Porter" <porter@...unc.edu>, "Jarkko Sakkinen"
> <jarkko.sakkinen@...ux.intel.com>, "Andi Kleen" <ak@...ux.intel.com>, "linux-kernel" <linux-kernel@...r.kernel.org>,
> "bp" <bp@...en8.de>, "Andy Lutomirski" <luto@...nel.org>, "Dave Hansen" <dave.hansen@...el.com>, "Tony Luck"
> <tony.luck@...el.com>, "Ravi V Shankar" <ravi.v.shankar@...el.com>, "chang seok bae" <chang.seok.bae@...el.com>
> Gesendet: Dienstag, 26. Mai 2020 10:12:02
> Betreff: RE: Re: [PATCH v12 00/18] Enable FSGSBASE instructions

> From: Richard Weinberger
>> Sent: 25 May 2020 08:55
> ...
>> P: Sadly too. Mostly because customer has custom module and forgot to set it GPL
> 
> You want us to lie that custom modules are GPL?

No. Of course not.

But after thinking twice most guys realize that the have to use GPL
no matter whether they are using just EXPORT_SYMBOL() stuff or not.

But this is a completely different topic and something for company lawyers.

Thanks,
//richard