Hi Nadia,
As part of the licensing assessment on pahole [0] that I am making for
Debian, I realized that file hash.h in both pahole [1] and the kernel
[2] comes without any licensing specification.
Could you please make an explicit choice and maybe provide patches?
Kind regards,
Domenico
[0] https://git.kernel.org/pub/scm/devel/pahole/pahole.git/
[1] https://git.kernel.org/pub/scm/devel/pahole/pahole.git/tree/hash.h
[2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/include/linux/hash.h
--
3B10 0CA1 8674 ACBA B4FE FCD2 CE5B CF17 9960 DE13
Ben Finney <[email protected]> writes:
> Domenico Andreoli <[email protected]> writes:
>
> > the situation of dwarves-dfsg improved a lot over the weekend
>
> That's good to hear. What is the event you're referring to? Can you give
> a URL to something that describes this change?
Upstream (in CC) reacted to my request of clarification and patches
have been applied upstream and on Salsa. See bug 919356 [0] (please
keep in CC).
> > the only knot left is now the license of hash.h
> >
> > This file is also present in the kernel [0] with an updated copyright
> > but still without license.
>
> The file you show (in the Linux code base) seems likely to have an
> equivalent implementation under a different license, from some other
> code base.
This will require research and work unlikely to be done before Buster
release. Are we going to drop this package for now?
> > I received a private email from somebody in the kernel community who
> > already tried to contact Nadia in the past but did not get any reply.
>
> Thank you also for contacting the Linux developers forum to ask
> <URL:https://www.mail-archive.com/[email protected]/msg1900588.html>.
(also in CC now)
> > I think that pushing it to non-free is formally the right thing but I
> > actually feel it's not the right thing.
>
> To know that work (that file) is free software, we need a clear grant of
> some specific license, for that work.
>
> If the work is not free, it would be incorrect to have the work in Debian.
Is it possible that for the kernel it is instead correct because it is,
as whole, covered by its COPYING?
> Alternatives, for complying with the Debian Free Software Guidelines with
> this package, include:
>
> * Find a credible grant of license under some GPL-compatible free
> license to that exact file. Document that explicit grant in the Debian
> package. This demonstrates the work is DFSG-free.
>
> * Convince ‘dwarves-dfsg’ upstream to replace that file with a different
> implementation (I don't know whether such an implementation exists)
> under a license compatible with the same version of GNU GPL. Document
> that explicit grant in the Debian package. This demonstrates the
> modified work is DFSG-free.
Arnaldo, what priority would you give to this task?
>
> * Replace that file in Debian only, with a different implementation as
> above. Document that explicit grant in the Debian package. This
> demonstrates the modified Debian package is DFSG-free.
>
> * Move the work to the ‘non-free’ area.
>
> * Remove the work altogether.
>
> Those are in descending order of (my recommended) preference.
Thanks,
Domenico
[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919356
--
3B10 0CA1 8674 ACBA B4FE FCD2 CE5B CF17 9960 DE13
On 1/23/19 9:50 AM, Domenico Andreoli wrote:
> Ben Finney <[email protected]> writes:
>> Domenico Andreoli <[email protected]> writes:
>>
>>> the situation of dwarves-dfsg improved a lot over the weekend
>>
>> That's good to hear. What is the event you're referring to? Can you give
>> a URL to something that describes this change?
>
> Upstream (in CC) reacted to my request of clarification and patches
> have been applied upstream and on Salsa. See bug 919356 [0] (please
> keep in CC).
>
>>> the only knot left is now the license of hash.h
>>>
>>> This file is also present in the kernel [0] with an updated copyright
>>> but still without license.
>>
>> The file you show (in the Linux code base) seems likely to have an
>> equivalent implementation under a different license, from some other
>> code base.
>
> This will require research and work unlikely to be done before Buster
> release. Are we going to drop this package for now?
>
>>> I received a private email from somebody in the kernel community who
>>> already tried to contact Nadia in the past but did not get any reply.
>>
>> Thank you also for contacting the Linux developers forum to ask
>> <URL:https://www.mail-archive.com/[email protected]/msg1900588.html>.
>
> (also in CC now)
>
>>> I think that pushing it to non-free is formally the right thing but I
>>> actually feel it's not the right thing.
>>
>> To know that work (that file) is free software, we need a clear grant of
>> some specific license, for that work.
>>
>> If the work is not free, it would be incorrect to have the work in Debian.
>
> Is it possible that for the kernel it is instead correct because it is,
> as whole, covered by its COPYING?
>
>> Alternatives, for complying with the Debian Free Software Guidelines with
>> this package, include:
>>
>> * Find a credible grant of license under some GPL-compatible free
>> license to that exact file. Document that explicit grant in the Debian
>> package. This demonstrates the work is DFSG-free.
>>
>> * Convince ‘dwarves-dfsg’ upstream to replace that file with a different
>> implementation (I don't know whether such an implementation exists)
>> under a license compatible with the same version of GNU GPL. Document
>> that explicit grant in the Debian package. This demonstrates the
>> modified work is DFSG-free.
>
> Arnaldo, what priority would you give to this task?
>
>>
>> * Replace that file in Debian only, with a different implementation as
>> above. Document that explicit grant in the Debian package. This
>> demonstrates the modified Debian package is DFSG-free.
>>
>> * Move the work to the ‘non-free’ area.
>>
>> * Remove the work altogether.
>>
>> Those are in descending order of (my recommended) preference.
>
> Thanks,
> Domenico
>
> [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919356
>
It was [pointed out] by one of our license group that [hash.h] is the
same that has a GPL-2+ in [fio] which has a signed-off-by.
References:
[pointed out]
https://bugs.gentoo.org/677586#c1
[hash.h]
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/fio.git/commit/hash.h?id=bdc7211e190482f0c17c109a0d90834a6611be1c
[fio]
https://metadata.ftp-master.debian.org/changelogs/main/f/fio/fio_3.12-2_copyright
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
On Mon, Feb 11, 2019 at 12:08:32AM +0100, Kristian Fiskerstrand wrote:
> On 1/23/19 9:50 AM, Domenico Andreoli wrote:
> > Ben Finney <[email protected]> writes:
> >> Domenico Andreoli <[email protected]> writes:
[...]
> >>> the only knot left is now the license of hash.h
> >>>
> >>> This file is also present in the kernel [0] with an updated copyright
> >>> but still without license.
[...]
> >> To know that work (that file) is free software, we need a clear grant of
> >> some specific license, for that work.
> >>
> >> If the work is not free, it would be incorrect to have the work in Debian.
> >
> > Is it possible that for the kernel it is instead correct because it is,
> > as whole, covered by its COPYING?
> >
> >> Alternatives, for complying with the Debian Free Software Guidelines with
> >> this package, include:
> >>
> >> * Find a credible grant of license under some GPL-compatible free
> >> license to that exact file. Document that explicit grant in the Debian
> >> package. This demonstrates the work is DFSG-free.
> >>
> >> * Convince ???dwarves-dfsg??? upstream to replace that file with a different
> >> implementation (I don't know whether such an implementation exists)
> >> under a license compatible with the same version of GNU GPL. Document
> >> that explicit grant in the Debian package. This demonstrates the
> >> modified work is DFSG-free.
> >>
> >> * Replace that file in Debian only, with a different implementation as
> >> above. Document that explicit grant in the Debian package. This
> >> demonstrates the modified Debian package is DFSG-free.
> >>
> >> * Move the work to the ???non-free??? area.
> >>
> >> * Remove the work altogether.
> >>
> >> Those are in descending order of (my recommended) preference.
[...]
> It was [pointed out] by one of our license group that [hash.h] is the
> same that has a GPL-2+ in [fio] which has a signed-off-by.
>
> References:
> [pointed out]
> https://bugs.gentoo.org/677586#c1
>
> [hash.h]
> https://git.kernel.org/pub/scm/linux/kernel/git/axboe/fio.git/commit/hash.h?id=bdc7211e190482f0c17c109a0d90834a6611be1c
Yes, the Signed-off-by is from Jens Axboe (in CC) but he's not the
original author, I guess he just copied the file as Arnaldo did. The
file he committed has not any reference to the license.
> [fio]
> https://metadata.ftp-master.debian.org/changelogs/main/f/fio/fio_3.12-2_copyright
I'm afraid that this entry in wrong. I'll seek confirmation with Martin Steigerwald.
Regards,
Domenico
--
3B10 0CA1 8674 ACBA B4FE FCD2 CE5B CF17 9960 DE13
>>>>> On Mon, 11 Feb 2019, Domenico Andreoli wrote:
> On Mon, Feb 11, 2019 at 12:08:32AM +0100, Kristian Fiskerstrand wrote:
>> It was [pointed out] by one of our license group that [hash.h] is the
>> same that has a GPL-2+ in [fio] which has a signed-off-by.
>>
>> References:
>> [pointed out]
>> https://bugs.gentoo.org/677586#c1
>>
>> [hash.h]
>> https://git.kernel.org/pub/scm/linux/kernel/git/axboe/fio.git/commit/hash.h?id=bdc7211e190482f0c17c109a0d90834a6611be1c
> Yes, the Signed-off-by is from Jens Axboe (in CC) but he's not the
> original author, I guess he just copied the file as Arnaldo did. The
> file he committed has not any reference to the license.
>> [fio]
>> https://metadata.ftp-master.debian.org/changelogs/main/f/fio/fio_3.12-2_copyright
> I'm afraid that this entry in wrong. I'll seek confirmation with
> Martin Steigerwald.
Not sure if this will help, but hash.h originally appeared in
Linux 2.5.7. In the following commit one can see that most of its code
was moved or copied from mm/filemap.c:
https://git.kernel.org/pub/scm/linux/kernel/git/tglx/history.git/commit/?id=882ad449046cec136c484dd2b3659fb4c683e0a3
filemap.c has a copyright line by Linus, but git blame shows that
the relevant code was added in 2002 with a commit by Rik van Riel:
https://git.kernel.org/pub/scm/linux/kernel/git/tglx/history.git/commit/?id=e5191c50d12621e04f8bc247dcb6a0f4ad76ae26
The relevant thread in LKML is here:
https://lkml.org/lkml/2002/2/18/1970
Ulrich
>>>>> On Mon, 11 Feb 2019, Ulrich Mueller wrote:
>>>>> On Mon, 11 Feb 2019, Domenico Andreoli wrote:
>> On Mon, Feb 11, 2019 at 12:08:32AM +0100, Kristian Fiskerstrand wrote:
>>> It was [pointed out] by one of our license group that [hash.h] is the
>>> same that has a GPL-2+ in [fio] which has a signed-off-by.
>>>
>>> References:
>>> [pointed out]
>>> https://bugs.gentoo.org/677586#c1
>>>
>>> [hash.h]
>>> https://git.kernel.org/pub/scm/linux/kernel/git/axboe/fio.git/commit/hash.h?id=bdc7211e190482f0c17c109a0d90834a6611be1c
>> Yes, the Signed-off-by is from Jens Axboe (in CC) but he's not the
>> original author, I guess he just copied the file as Arnaldo did. The
>> file he committed has not any reference to the license.
>>> [fio]
>>> https://metadata.ftp-master.debian.org/changelogs/main/f/fio/fio_3.12-2_copyright
>> I'm afraid that this entry in wrong. I'll seek confirmation with
>> Martin Steigerwald.
> Not sure if this will help, but hash.h originally appeared in
> Linux 2.5.7. In the following commit one can see that most of its code
> was moved or copied from mm/filemap.c:
> https://git.kernel.org/pub/scm/linux/kernel/git/tglx/history.git/commit/?id=882ad449046cec136c484dd2b3659fb4c683e0a3
> filemap.c has a copyright line by Linus, but git blame shows that
> the relevant code was added in 2002 with a commit by Rik van Riel:
> https://git.kernel.org/pub/scm/linux/kernel/git/tglx/history.git/commit/?id=e5191c50d12621e04f8bc247dcb6a0f4ad76ae26
> The relevant thread in LKML is here:
> https://lkml.org/lkml/2002/2/18/1970
Sorry, that link should read:
https://lkml.org/lkml/2002/2/18/197
On 2/11/19 3:50 AM, Martin Steigerwald wrote:
> Adding in [email protected], as I am not sure whether the oracle.com address
> from Jens is actually valid / up to date.
>
> Domenico Andreoli - 11.02.19, 08:22:
>> On Mon, Feb 11, 2019 at 12:08:32AM +0100, Kristian Fiskerstrand wrote:
>> >
> Mit freundlichen Grüßen / With kind regards
>
> Martin Steigerwald •
> Proact Deutschland GmbH
>
> Trainer
>
> Telefon: *+49 911 30999 0* <tel:+49%20911%2030999%200> •
> Fax: *+49 911 30999 99* <tel:>
>
> Südwestpark 43 •
> 90449 Nürnberg •
> Germany
>
> *[email protected]* <mailto:[email protected]> •
> *http://www.proact.de* <https://www.proact.de/>
>
>
> Amtsgericht Nürnberg
> •
> HRB 18320
>
> Geschäftsführer:
> Oliver Kügow •
> Richard Müller •
> Jakob Høholdt
> •
> Peter Mikael Javestad
>
>
> – Delivering Business Agility –
>
>
>
> On 1/23/19 9:50 AM, Domenico Andreoli wrote:
>> > > Ben Finney <[email protected]> writes:
>> > >> Domenico Andreoli <[email protected]> writes:
>> [...]
>>
>> > >>> the only knot left is now the license of hash.h
>> > >>>
>> > >>> This file is also present in the kernel [0] with an updated copyright
>> > >>> but still without license.
>>
>> [...]
>>
>> > >> To know that work (that file) is free software, we need a clear grant
>> > >> of
>> > >> some specific license, for that work.
>> > >>
>> > >> If the work is not free, it would be incorrect to have the work in
>> > >> Debian.
>> > >
>> > > Is it possible that for the kernel it is instead correct because it is,
>> > > as whole, covered by its COPYING?
>> > >
>> > >> Alternatives, for complying with the Debian Free Software Guidelines
>> > >> with
>> > >> this package, include:
>> > >>
>> > >> * Find a credible grant of license under some GPL-compatible free
>> > >>
>> > >> license to that exact file. Document that explicit grant in the
>> > >> Debian
>> > >> package. This demonstrates the work is DFSG-free.
>> > >>
>> > >> * Convince ???dwarves-dfsg??? upstream to replace that file with a
>> > >> different> >>
>> > >> implementation (I don't know whether such an implementation exists)
>> > >> under a license compatible with the same version of GNU GPL. Document
>> > >> that explicit grant in the Debian package. This demonstrates the
>> > >> modified work is DFSG-free.
>> > >>
>> > >> * Replace that file in Debian only, with a different implementation as
>> > >>
>> > >> above. Document that explicit grant in the Debian package. This
>> > >> demonstrates the modified Debian package is DFSG-free.
>> > >>
>> > >> * Move the work to the ???non-free??? area.
>> > >>
>> > >> * Remove the work altogether.
>> > >>
>> > >> Those are in descending order of (my recommended) preference.
>>
>> [...]
>>
>> > It was [pointed out] by one of our license group that [hash.h] is the
>> > same that has a GPL-2+ in [fio] which has a signed-off-by.
>> >
>> > References:
>> > [pointed out]
>> > https://bugs.gentoo.org/677586#c1
>> >
>> > [hash.h]
>> > https://git.kernel.org/pub/scm/linux/kernel/git/axboe/fio.git/commit/hash.
>> > h?id=bdc7211e190482f0c17c109a0d90834a6611be1c
>> Yes, the Signed-off-by is from Jens Axboe (in CC) but he's not the
>> original author, I guess he just copied the file as Arnaldo did. The
>> file he committed has not any reference to the license.
>>
>> > [fio]
>> > https://metadata.ftp-master.debian.org/changelogs/main/f/fio/fio_3.12-2_co
>> > pyright
>> I'm afraid that this entry in wrong. I'll seek confirmation with Martin
>> Steigerwald.
>
> Which entry to you refer to? I assume the one about hash.h.
>
> Well the file has in its header:
>
> /* Fast hashing routine for a long.
> (C) 2002 William Lee Irwin III, IBM */
>
> /*
> * Knuth recommends primes in approximately golden ratio to the maximum
> * integer representable by a machine word for multiplicative hashing.
> * Chuck Lever verified the effectiveness of this technique:
> * http://www.citi.umich.edu/techreports/reports/citi-tr-00-1.pdf
> *
> * These primes are chosen to be bit-sparse, that is operations on
> * them can use shifts and additions instead of multiplications for
> * machines where multiplications are slow.
> */
>
> It has been quite a while ago. I bet back then I did not regard this as
> license information since it does not specify a license. Thus I assumed it to
> be GPL-2 as the other files which have no license boiler plate. I.e.: Check file
> is it has different license, if not, then assume it has license as specified in
> COPYING.
>
> Not specifying a license can however also mean in this context that it has no
> license as the file contains copyright information from another author.
>
> Of course I can update copyright file in case my conclusion from a long time
> ago was wrong.
>
> Jens?
Right, if nothing else is noted, it's GPL v2.
--
Jens Axboe