From: Viktor Malik <vmalik@redhat.com>
To: bpf@vger.kernel.org
Cc: Andrii Nakryiko <andrii@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>, Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Tom Rix <trix@redhat.com>, Viktor Malik <vmalik@redhat.com>
Subject: [PATCH bpf-next 0/3] libbpf: fix several issues reported by static analysers
Date: Wed, 1 Mar 2023 09:53:52 +0100 [thread overview]
Message-ID: <cover.1677658777.git.vmalik@redhat.com> (raw)
Fixing several issues reported by Coverity and Clang Static Analyzer
(scan-build) for libbpf, mostly removing unnecessary symbols and
assignments.
No functional changes should be introduced.
Viktor Malik (3):
libbpf: remove unnecessary ternary operator
libbpf: remove several dead assignments
libbpf: cleanup linker_append_elf_relos
tools/lib/bpf/btf.c | 2 --
tools/lib/bpf/libbpf.c | 3 +--
tools/lib/bpf/linker.c | 11 ++---------
tools/lib/bpf/relo_core.c | 3 ---
4 files changed, 3 insertions(+), 16 deletions(-)
--
2.39.1
next reply other threads:[~2023-03-01 8:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 8:53 Viktor Malik [this message]
2023-03-01 8:53 ` [PATCH bpf-next 1/3] libbpf: remove unnecessary ternary operator Viktor Malik
2023-03-01 8:53 ` [PATCH bpf-next 2/3] libbpf: remove several dead assignments Viktor Malik
2023-03-01 8:53 ` [PATCH bpf-next 3/3] libbpf: cleanup linker_append_elf_relos Viktor Malik
2023-03-01 19:20 ` [PATCH bpf-next 0/3] libbpf: fix several issues reported by static analysers 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=cover.1677658777.git.vmalik@redhat.com \
--to=vmalik@redhat.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=trix@redhat.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