linux-kernel - Re: PostgreSQL licensed code on Linux

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: <20180529210025.GB3487@kmo-pixel>
Date:   Tue, 29 May 2018 17:00:25 -0400
From:   Kent Overstreet <kent.overstreet@...il.com>
To:     "Theodore Y. Ts'o" <tytso@....edu>,
        "Luis R. Rodriguez" <mcgrof@...not-panic.com>,
        Coly Li <colyli@...e.de>,
        Ciaran Farrell <ciaran.farrell@...e.com>,
        One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
        linux-bcache@...r.kernel.org,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Philippe Ombredanne <pombredanne@...b.com>,
        Kate Stewart <kstewart@...uxfoundation.org>,
        Jonas Oberg <jonas@...e.org>
Subject: Re: PostgreSQL licensed code on Linux

On Tue, May 29, 2018 at 04:51:44PM -0400, Theodore Y. Ts'o wrote:
> On Tue, May 29, 2018 at 03:26:43PM -0400, Kent Overstreet wrote:
> > > That seems to indicate that we've had already PostgreSQL licensed code on
> > > Linux since Kent's addition of bcache to Linux in 2013. The portion of code
> > > is rather small though, to me it seems to cover only crc_table[],
> > > bch_crc64_update(), and bch_crc64().
> >
> > > As silly as it may be we should split out the PostgreSQL licensed code from
> > > drivers/md/bcache/util.c into its own file and while at it clarify the
> > > license.
> 
> While we're at it maybe we should move the crc-64 code to lib and/or
> crypto, alongside our support for crc-8, crc-16, and crc-32
> algorithms?  That way if there are other potential users for crc-64,
> they will be less likely to re-invent the wheel....

Yeah, this came up because Coly wanted to do that, but needed to know what to
put in MODULE_LICENSE().