linux-kernel - Re: [copyleft-next] Re: [PATCH v9 3/6] selftests: add tests

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: <CAGT84B35yEjPxtu=cShoxCNzi8kaYDBbHDsu9-g0UhdFrCS6Lg@mail.gmail.com>
Date:   Tue, 14 Dec 2021 14:31:46 -0500
From:   Richard Fontana <fontana@...rpeleven.org>
To:     Discussion and development of copyleft-next 
        <copyleft-next@...ts.fedorahosted.org>
Cc:     Greg KH <gregkh@...uxfoundation.org>,
        Petr Mladek <pmladek@...e.com>, akpm@...ux-foundation.org,
        jeyu@...nel.org, tglx@...utronix.de, linux-kernel@...r.kernel.org,
        rostedt@...dmis.org, shuah@...nel.org, keescook@...omium.org,
        linux-fsdevel@...r.kernel.org, linux-spdx@...r.kernel.org,
        tj@...nel.org, dan.j.williams@...el.com, bvanassche@....org,
        linux-kselftest@...r.kernel.org, joe@...ches.com,
        linux-doc@...r.kernel.org, linux-block@...r.kernel.org,
        minchan@...nel.org
Subject: Re: [copyleft-next] Re: [PATCH v9 3/6] selftests: add tests_sysfs module

 On Wed, Dec 8, 2021 at 8:52 PM Luis Chamberlain <mcgrof@...nel.org> wrote:
>
> On Fri, Dec 03, 2021 at 04:29:02PM +0100, Greg KH wrote:
> > On Fri, Oct 29, 2021 at 11:44:57AM -0700, Luis Chamberlain wrote:

> > > diff --git a/lib/test_sysfs.c b/lib/test_sysfs.c
> > > new file mode 100644
> > > index 000000000000..2a6ec072da60
> > > --- /dev/null
> > > +++ b/lib/test_sysfs.c
> > > @@ -0,0 +1,894 @@
> > > +// SPDX-License-Identifier: GPL-2.0-or-later OR copyleft-next-0.3.1
> >
> > Again, sorry, but no, I am going to object to this license as you are
> > only accessing a GPL-v2-only api.  Any other license on a file that
> > interacts with that, especially for core stuff like testing the
> > functionality of this code, needs to have that same license.  Sorry.
>
> Huh? The license is GPL-v2 compatible, and when used in the kernel the
> GPLv2 applies.
>
> Likewise, are you taking the position that permissively licensed code,
> say BSD or ISC licensed code, cannot use EXPORT_SYMBOL_GPL() symbols?

Just chiming in here, not really because of any association with the
copyleft-next license (or GPLv2 for that matter) but because of
general personal immersion in open source licensing. I would think
that code interacting with a GPLv2-only api could be under any
GPLv2-only-compatible license, such as ISC, GPLv2-or-later, or
copyleft-next. That said, of course kernel maintainers can establish
stricter policies around acceptable forms of licensing.

Richard