linux-kernel - Re: [PATCH] lib/string: Bring optimized memcmp from glibc

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: <4693ebde-e0e8-e9b0-6d89-9463e1d9c243@sony.com>
Date:   Wed, 21 Jul 2021 15:39:13 +0000
From:   <Peter.Enderborg@...y.com>
To:     <willy@...radead.org>
CC:     <hch@...radead.org>, <nborisov@...e.com>,
        <linux-kernel@...r.kernel.org>, <ndesaulniers@...gle.com>,
        <torvalds@...ux-foundation.org>, <linux-fsdevel@...r.kernel.org>,
        <david@...morbit.com>
Subject: Re: [PATCH] lib/string: Bring optimized memcmp from glibc

On 7/21/21 5:34 PM, Matthew Wilcox wrote:
> On Wed, Jul 21, 2021 at 03:17:53PM +0000, Peter.Enderborg@...y.com wrote:
>> On 7/21/21 4:51 PM, Matthew Wilcox wrote:
>>> On Wed, Jul 21, 2021 at 03:42:10PM +0100, Christoph Hellwig wrote:
>>>> On Wed, Jul 21, 2021 at 05:35:42PM +0300, Nikolay Borisov wrote:
>>>>>
>>>>> On 21.07.21 ??. 17:32, Christoph Hellwig wrote:
>>>>>> This seems to have lost the copyright notices from glibc.
>>>>>>
>>>>> I copied over only the code, what else needs to be brought up:
>>>>>
>>>>>  Copyright (C) 1991-2021 Free Software Foundation, Inc.
>>>>>    This file is part of the GNU C Library.
>>>>>    Contributed by Torbjorn Granlund (tege@...s.se).
>>>>>
>>>>> The rest is the generic GPL license txt ?
>>>> Last time I checked glibc is under LGPL.
>>> This particular file is under LGPL-2.1, so we can distribute it under
>>> GPL 2.
>>
>> Sure. But should not Torbjörn Granlund have some cred?
> 
> I didn't say we could remove his copyright.  It's clearly still
> copyright Torbjörn.
> 

Yes, but how?