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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5fb2159f-12cc-4395-ae53-b686d185be45@redhat.com>
Date: Mon, 28 Jul 2025 17:46:28 +0200
From: Thomas Huth <thuth@...hat.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Sean Christopherson <seanjc@...gle.com>,
 Paolo Bonzini <pbonzini@...hat.com>, Thomas Gleixner <tglx@...utronix.de>,
 Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
 Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
 "H. Peter Anvin" <hpa@...or.com>, kvm@...r.kernel.org,
 linux-kernel@...r.kernel.org, linux-spdx@...r.kernel.org
Subject: Re: [PATCH v2] arch/x86/kvm/ioapic: Remove license boilerplate with
 bad FSF address

On 28/07/2025 17.36, Greg Kroah-Hartman wrote:
> On Mon, Jul 28, 2025 at 05:28:43PM +0200, Thomas Huth wrote:
>> From: Thomas Huth <thuth@...hat.com>
>>
>> The Free Software Foundation does not reside in "59 Temple Place"
>> anymore, so we should not mention that address in the source code here.
>> But instead of updating the address to their current location, let's
>> rather drop the license boilerplate text here and use a proper SPDX
>> license identifier instead. The text talks about the "GNU *Lesser*
>> General Public License" and "any later version", so LGPL-2.1+ is the
>> right choice here.
>>
>> Signed-off-by: Thomas Huth <thuth@...hat.com>
>> ---
>>   v2: Don't use the deprecated LGPL-2.1+ identifier
> 
> If you look at the LICENSES/preferred/LGPL-2.1 file, it says to use:
> 	SPDX-License-Identifier: LGPL-2.1+
> 
> as the kernel's SPDX level is older than you might think.

Ok, got it, then please ignore this v2 and use v1 instead.

> Also, doesn't the scripts/spdxcheck.pl tool object to the "or-later"
> when you run it on the tree with this change in it?

I used the scripts/checkpatch.pl which is also supposed to check SPDX tags, 
and it did not complain...

  Thomas


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ