linux-kernel - Re: [PATCH] Corrected GPL license name

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: <5bb799e2-492b-49f2-b5f5-7e8f113bf56f@isovalent.com>
Date: Wed, 14 Feb 2024 15:14:46 +0000
From: Quentin Monnet <quentin@...valent.com>
To: Gianmarco Lusvardi <glusvardi@...teo.net>,
 Alexei Starovoitov <ast@...nel.org>, Daniel Borkmann <daniel@...earbox.net>,
 Andrii Nakryiko <andrii@...nel.org>
Cc: Martin KaFai Lau <martin.lau@...ux.dev>, Song Liu <song@...nel.org>,
 Yonghong Song <yonghong.song@...ux.dev>,
 John Fastabend <john.fastabend@...il.com>, KP Singh <kpsingh@...nel.org>,
 Stanislav Fomichev <sdf@...gle.com>, Hao Luo <haoluo@...gle.com>,
 Jiri Olsa <jolsa@...nel.org>, bpf@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Corrected GPL license name

2024-02-13 23:07 UTC+0000 ~ Gianmarco Lusvardi <glusvardi@...teo.net>
> The bpf_doc script refers to the GPL as the "GNU Privacy License".
> I strongly suspect that the author wanted to refer to the GNU General
> Public License, under which the Linux kernel is released, as, to the
> best of my knowledge, there is no license named "GNU Privacy License".
> 
> This patch corrects the license name in the script accordingly.
> 
> Signed-off-by: Gianmarco Lusvardi <glusvardi@...teo.net>
> ---
>  scripts/bpf_doc.py | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/scripts/bpf_doc.py b/scripts/bpf_doc.py
> index 61b7dddedc46..0669bac5e900 100755
> --- a/scripts/bpf_doc.py
> +++ b/scripts/bpf_doc.py
> @@ -513,7 +513,7 @@ eBPF programs can have an associated license, passed along with the bytecode
>  instructions to the kernel when the programs are loaded. The format for that
>  string is identical to the one in use for kernel modules (Dual licenses, such
>  as "Dual BSD/GPL", may be used). Some helper functions are only accessible to
> -programs that are compatible with the GNU Privacy License (GPL).
> +programs that are compatible with the GNU General Public License (GNU GPL).
>  
>  In order to use such helpers, the eBPF program must be loaded with the correct
>  license string passed (via **attr**) to the **bpf**\\ () system call, and this

Not sure how I came up with that one. Thanks for the fix!

Fixes: 56a092c89505 ("bpf: add script and prepare bpf.h for new helpers documentation")
Reviewed-by: Quentin Monnet <quentin@...valent.com>