From: Simon Horman <simon.horman@corigine.com>
To: Quentin Monnet <quentin@isovalent.com>
Cc: Luca Boccassi <bluca@debian.org>,
bpf@vger.kernel.org, bjorn@kernel.org, kuba@kernel.org,
ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org, daniel@zonque.org,
joe@ovn.org, jbacik@fb.com
Subject: Re: [PATCH] samples/bpf: relicense bpf_insn.h as GPL-2.0-only OR BSD-2-Clause
Date: Thu, 23 Sep 2021 16:10:34 +0200 [thread overview]
Message-ID: <20210923141034.GA12692@corigine.com> (raw)
In-Reply-To: <a92cd043-30e8-c26d-ffe9-3521322ce71b@isovalent.com>
On Thu, Sep 23, 2021 at 02:42:39PM +0100, Quentin Monnet wrote:
> 2021-09-23 11:41 UTC+0100 ~ Luca Boccassi <bluca@debian.org>
> > On Thu, 2021-09-23 at 01:05 +0100, luca.boccassi@gmail.com wrote:
> >> From: Luca Boccassi <bluca@debian.org>
> >>
> >> libbpf and bpftool have been dual-licensed to facilitate inclusion in
> >> software that is not compatible with GPL2-only (ie: Apache2), but the
> >> samples are still GPL2-only.
> >>
> >> Given these files are samples, they get naturally copied around. For
> >> example
> >> it is the case for samples/bpf/bpf_insn.h which was copied into the
> >> systemd
> >> tree:
> >> https://github.com/systemd/systemd/blob/main/src/shared/linux/bpf_insn.h
> >>
> >> Dual-license this header as GPL-2.0-only OR BSD-2-Clause to follow
> >> the same licensing used by libbpf and bpftool:
> >>
> >> 1bc38b8ff6cc ("libbpf: relicense libbpf as LGPL-2.1 OR BSD-2-Clause")
> >> 907b22365115 ("tools: bpftool: dual license all files")
> >>
> >> Signed-off-by: Luca Boccassi <bluca@debian.org>
> >> ---
> >> Most of systemd is (L)GPL2-or-later, which means there is no
> >> perceived
> >> incompatibility with Apache2 softwares and can thus be linked with
> >> OpenSSL 3.0. But given this GPL2-only header is included this is
> >> currently
> >> not possible.
> >> Dual-licensing this header solves this problem for us as we are
> >> scoping
> >> moving to OpenSSL 3.0, see:
> >>
> >> https://lists.freedesktop.org/archives/systemd-devel/2021-September/046882.html
> >>
> >> The authors of this file according to git log are:
> >>
> >> Alexei Starovoitov <ast@kernel.org>
> >> Björn Töpel <bjorn.topel@intel.com>
> >> Brendan Jackman <jackmanb@google.com>
> >> Chenbo Feng <fengc@google.com>
> >> Daniel Borkmann <daniel@iogearbox.net>
> >> Daniel Mack <daniel@zonque.org>
> >> Jakub Kicinski <jakub.kicinski@netronome.com>
> >> Jiong Wang <jiong.wang@netronome.com>
> >> Joe Stringer <joe@ovn.org>
> >> Josef Bacik <jbacik@fb.com>
> >>
> >> (excludes a commit adding the SPDX header)
> >>
> >> All authors and maintainers are CC'ed. An Acked-by from everyone in
> >> the
> >> above list of authors will be necessary.
> >>
> >> One could probably argue for relicensing all the samples/bpf/ files
> >> given both
> >> libbpf and bpftool are, however the authors list would be much larger
> >> and thus
> >> it would be much more difficult, so I'd really appreciate if this
> >> header could
> >> be handled first by itself, as it solves a real license
> >> incompatibility issue
> >> we are currently facing.
> >>
> >> samples/bpf/bpf_insn.h | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/samples/bpf/bpf_insn.h b/samples/bpf/bpf_insn.h
> >> index aee04534483a..29c3bb6ad1cd 100644
> >> --- a/samples/bpf/bpf_insn.h
> >> +++ b/samples/bpf/bpf_insn.h
> >> @@ -1,4 +1,4 @@
> >> -/* SPDX-License-Identifier: GPL-2.0 */
> >> +/* SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) */
> >> /* eBPF instruction mini library */
> >> #ifndef __BPF_INSN_H
> >> #define __BPF_INSN_H
> >
> > Got "address not found" for the following:
> >
> > Björn Töpel <bjorn.topel@intel.com>
> > Jakub Kicinski <jakub.kicinski@netronome.com>
> > Jiong Wang <jiong.wang@netronome.com>
> >
> > Trying again with different aliases from more recent commits for Björn
> > and Jakub.
> >
> > I cannot find other commits from Jiong with a different email address -
> > Jakub, do you happen to know how we can reach Jiong? Perhaps it's not
> > necessary as it's Netronome that owns the copyright and thus your ack
> > would cover both contributions?
> >
>
> Hi Luca, I believe Simon can handle this for Netronome, I'm adding him
> in copy.
Yes, in the recent past we have handled a similar request like this:
Acked-by: Simon Horman <simon.horman@corigine.com>
next prev parent reply other threads:[~2021-09-23 14:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 0:05 [PATCH] samples/bpf: relicense bpf_insn.h as GPL-2.0-only OR BSD-2-Clause luca.boccassi
2021-09-23 10:41 ` Luca Boccassi
2021-09-23 13:42 ` Quentin Monnet
2021-09-23 14:10 ` Simon Horman [this message]
2021-09-27 14:07 ` Luca Boccassi
2021-09-27 14:11 ` Daniel Mack
2021-09-27 14:27 ` Luca Boccassi
2021-09-27 14:39 ` Josef Bacik
2021-09-28 15:44 ` Luca Boccassi
2021-09-29 11:01 ` Björn Töpel
2021-09-29 11:05 ` Luca Boccassi
2021-09-29 11:26 ` Magnus Karlsson
2021-09-29 11:27 ` Luca Boccassi
[not found] ` <CA+i-1C3sjrwtskbSZzera7ANL8dTiVWMBwLRhe=+1Ft6NgfL=A@mail.gmail.com>
2021-09-28 19:09 ` Joe Stringer
[not found] ` <CAMOXUJ=gLLCDv0ZuEz77Qvepx9r0uTfy3J3phWuGPMQXsM1FGA@mail.gmail.com>
2021-09-28 19:12 ` Chenbo Feng
2021-09-29 16:06 ` Luca Boccassi
2021-09-29 16:10 ` Daniel Borkmann
2021-09-29 16:37 ` Luca Boccassi
2021-09-29 16:10 ` patchwork-bot+netdevbpf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210923141034.GA12692@corigine.com \
--to=simon.horman@corigine.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=bluca@debian.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=daniel@zonque.org \
--cc=jbacik@fb.com \
--cc=joe@ovn.org \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=quentin@isovalent.com \
--cc=songliubraving@fb.com \
--cc=yhs@fb.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).