Skip to contentSkip to conversation

libbpf: relicense libbpf as LGPL-2.1 OR BSD-2-Clause

PATCH Daniel Borkmann 2 participants 2 messages Oct 8, 2018 1 message not in the archive

Subsystems (2)
lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

Daniel Borkmann

author Applied
#1 lore raw
Quoted 10 lines · Alexei Starovoitov

libbpf is maturing as a library and gaining features that no other bpf libraries support (BPF Type Format, bpf to bpf calls, etc)
Many Apache2 licensed projects (like bcc, bpftrace, gobpf, cilium, etc) would like to use libbpf, but cannot do this yet, since Apache Foundation explicitly states that LGPL is incompatible with Apache2.
Hence let's relicense libbpf as dual license LGPL-2.1 or BSD-2-Clause, since BSD-2 is compatible with Apache2.
Dual LGPL or Apache2 is invalid combination.
Fix license mistake in Makefile as well.

Quoted 15 lines

Applied to bpf-next, thanks!

#2 lore raw
Quoted 27 lines · On Mon, 8 Oct 2018 10:15:10 +0200 Daniel Borkmann <[email protected]> wrote:
Quoted 10 lines · Alexei Starovoitov

libbpf is maturing as a library and gaining features that no other bpf libraries support (BPF Type Format, bpf to bpf calls, etc)
Many Apache2 licensed projects (like bcc, bpftrace, gobpf, cilium, etc) would like to use libbpf, but cannot do this yet, since Apache Foundation explicitly states that LGPL is incompatible with Apache2.
Hence let's relicense libbpf as dual license LGPL-2.1 or BSD-2-Clause, since BSD-2 is compatible with Apache2.
Dual LGPL or Apache2 is invalid combination.
Fix license mistake in Makefile as well.

Quoted 15 lines
Quoted 1 line

Applied to bpf-next, thanks!

For the public record:

I do know, this ack will not reach the git-log, but given I have code in the lib, I want to show that I support and ack this re-license.

Signature · 4 lines
Best regards,
  Jesper Dangaard Brouer
  MSc.CS, Principal Kernel Engineer at Red Hat
  LinkedIn: http://www.linkedin.com/in/brouer