linux-kernel - Re: [RFC PATCH v3] selftest/x86/meltdown: Add a selftest for meltdown

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]

Message-ID: <Y3XQZFyiXYc9mJ1Y@kroah.com>
Date:   Thu, 17 Nov 2022 07:10:44 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Dave Hansen <dave.hansen@...el.com>
Cc:     Aaron Lu <aaron.lu@...el.com>,
        Dave Hansen <dave.hansen@...ux.intel.com>,
        Tony Luck <tony.luck@...el.com>,
        "Yin, Fengwei" <fengwei.yin@...el.com>,
        "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
        "Huang, Ying" <ying.huang@...el.com>,
        linux-kselftest@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH v3] selftest/x86/meltdown: Add a selftest for meltdown

On Wed, Nov 16, 2022 at 02:57:22PM -0800, Dave Hansen wrote:
> On 11/14/22 22:54, Greg KH wrote:
> > On Tue, Nov 15, 2022 at 10:15:03AM +0800, Aaron Lu wrote:
> >> I came to the conclusion that this work is OK to submit with all of the
> >> steps I listed above (copyright notices, license terms and relicensing)
> >> by strictly following all of the processes required by my employer.
> >>
> >> This does not include a Signed-off-by from a corporate attorney.
> > Please get that, as that is what I asked for in order for us to be able
> > to accept this type of change.
> 
> Hi Greg,
> 
> Can you share any more of what triggered this new requirement?

You are taking source from a non-Intel developer under a different
license and adding copyright and different license information to it.
Because of all of that, I have the requirement that I want to know that
Intel legal has vetted all of this and agrees with the conclusions that
you all are stating.

This isn't a new type of requirement, I make this request to many other
companies that do things that are not "normal" when it comes to licenses
and copyrights so as to ensure that all is ok.

thanks,

greg k-h