BPF List
 help / color / mirror / Atom feed
From: Geliang Tang <geliang@kernel.org>
To: Andrii Nakryiko <andrii@kernel.org>,
	Eduard Zingerman <eddyz87@gmail.com>,
	Mykola Lysenko <mykolal@fb.com>,
	Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Martin KaFai Lau <martin.lau@linux.dev>,
	Song Liu <song@kernel.org>,
	Yonghong Song <yonghong.song@linux.dev>,
	John Fastabend <john.fastabend@gmail.com>,
	KP Singh <kpsingh@kernel.org>, Hao Luo <haoluo@google.com>,
	Jiri Olsa <jolsa@kernel.org>, Shuah Khan <shuah@kernel.org>
Cc: Geliang Tang <tanggeliang@kylinos.cn>,
	bpf@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: [PATCH bpf-next v2 0/3] handle errno ENOTSUPP
Date: Fri, 12 Jul 2024 22:24:15 +0800	[thread overview]
Message-ID: <cover.1720791488.git.tanggeliang@kylinos.cn> (raw)

From: Geliang Tang <tanggeliang@kylinos.cn>

v2:
 - patch 1, only commit log updated
 - update patch 2
   - add an unsigned variable
   - use "switch-case"
   - only "Operation not supported", no (-524) in string
 - patch 3, a now one

This patchset contains three fixes for handling errno ENOTSUPP.

Patch 1 fixes the return value of fixup_call_args() to make sure
ENOTSUPP is returned to user space correctly.
Patch 2 handles ENOTSUPP in libbpf_strerror_r() in libbpf.
Patch 3 includes str_error.h in BPF selftests, and drop duplicate
ENOTSUPP definitions.

Geliang Tang (3):
  bpf: verifier: Fix return value of fixup_call_args
  libbpf: handle ENOTSUPP in libbpf_strerror_r
  selftests/bpf: Drop duplicate ENOTSUPP definitions

 kernel/bpf/verifier.c                          |  6 +++---
 tools/lib/bpf/str_error.c                      | 18 +++++++++++++-----
 tools/lib/bpf/str_error.h                      |  4 ++++
 .../selftests/bpf/prog_tests/bpf_tcp_ca.c      |  4 ----
 .../selftests/bpf/prog_tests/lsm_cgroup.c      |  4 ----
 .../selftests/bpf/prog_tests/sock_addr.c       |  4 ----
 tools/testing/selftests/bpf/test_maps.c        |  4 ----
 tools/testing/selftests/bpf/test_verifier.c    |  4 ----
 tools/testing/selftests/bpf/testing_helpers.h  |  1 +
 9 files changed, 21 insertions(+), 28 deletions(-)

-- 
2.43.0


             reply	other threads:[~2024-07-12 14:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-12 14:24 Geliang Tang [this message]
2024-07-12 14:24 ` [PATCH bpf-next v2 1/3] bpf: verifier: Fix return value of fixup_call_args Geliang Tang
2024-07-12 14:24 ` [PATCH bpf-next v2 2/3] libbpf: handle ENOTSUPP in libbpf_strerror_r Geliang Tang
2024-07-12 14:24 ` [PATCH bpf-next v2 3/3] selftests/bpf: Drop duplicate ENOTSUPP definitions Geliang Tang

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=cover.1720791488.git.tanggeliang@kylinos.cn \
    --to=geliang@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=mykolal@fb.com \
    --cc=shuah@kernel.org \
    --cc=song@kernel.org \
    --cc=tanggeliang@kylinos.cn \
    --cc=yonghong.song@linux.dev \
    /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