Commit 2c91a688 authored Feb 13, 2024 by Gianmarco Lusvardi Committed by sanglipeng1 Jul 23, 2024

bpf, scripts: Correct GPL license name

stable inclusion
from stable-v5.10.211
commit b42b801abada4d346aa989e523b625051effd593
category: bugfix
bugzilla: https://gitee.com/openeuler/kernel/issues/IAF2J4

Reference: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b42b801abada4d346aa989e523b625051effd593



--------------------------------

[ Upstream commit e37243b65d528a8a9f8b9a57a43885f8e8dfc15c ]

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.

Fixes: 56a092c8 ("bpf: add script and prepare bpf.h for new helpers documentation")
Signed-off-by: Gianmarco Lusvardi <glusvardi@posteo.net>
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Reviewed-by: Quentin Monnet <quentin@isovalent.com>
Link: https://lore.kernel.org/bpf/20240213230544.930018-3-glusvardi@posteo.net


Signed-off-by: Sasha Levin <sashal@kernel.org>
Signed-off-by: sanglipeng1 <sanglipeng1@jd.com>

parent cff7652a

scripts/bpf_helpers_doc.py

+1 −1

Original line number	Diff line number	Diff line
		@@ -284,7 +284,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