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  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:   Thu, 28 Feb 2019 11:09:18 -0500
From:   Steven Rostedt <>
To:     Greg KH <>
Cc:     Joel Fernandes <>,
        Masami Hiramatsu <>,,
        Andrew Morton <>,,,,
        Dan Williams <>,
        Guenter Roeck <>,
        Jonathan Corbet <>,,
        Kees Cook <>,,,,,
        Manoj Rao <>,
        Masahiro Yamada <>,,
        "Peter Zijlstra (Intel)" <>,,,
        Shuah Khan <>,
        Thomas Gleixner <>,
Subject: Re: [PATCH v3 1/2] Provide in-kernel headers for making it easy to
 extend the kernel

On Thu, 28 Feb 2019 16:45:13 +0100
Greg KH <> wrote:

> On Thu, Feb 28, 2019 at 10:37:41AM -0500, Joel Fernandes wrote:
> > In any case, it is not practical to provide headers for every kernel version on
> > the system image and maintain them, it will take up too much space and has to
> > be periodically packaged. Not to mention that there will be kernel versions
> > that are booting Android that simply don't have anyone maintaining headers
> > for. So the proposed solution is an easier path.  
> I totally agree with this, and with your proposed patches, just wanting
> to clear up some potential anti-GPL-FUD before it got spread any further :)

I would believe that the decision of saying it is "not allowed" is not
about it being illegal, but more of a "we would then need to keep track
of every GPL code and all the specific versions in every package that we
ship such that we will have to provide it if someone were to ask for
it", which would be required by the license. And that can be quite a

-- Steve

Powered by blists - more mailing lists