From: Kumar Kartikeya Dwivedi <memxor@gmail.com>
To: bpf@vger.kernel.org
Cc: "Kumar Kartikeya Dwivedi" <memxor@gmail.com>,
"Alexei Starovoitov" <ast@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Andrii Nakryiko" <andrii@kernel.org>,
"Toke Høiland-Jørgensen" <toke@redhat.com>,
netdev@vger.kernel.org
Subject: [PATCH bpf-next 0/3] Fixes for TC-BPF series
Date: Sat, 12 Jun 2021 08:04:59 +0530 [thread overview]
Message-ID: <20210612023502.1283837-1-memxor@gmail.com> (raw)
These are a few simple cleanups. Two of these hopefully silence the coverity
warnings. Even though there is no real bug here, the report is valid as per
language rules, and overall it does make the code a bit simpler. There's one
other patch to add the forgotten NLM_F_EXCL that I spotted while doing this.
Andrii, would you be able to tell whether this silences the warnings? I wasn't
able to figure out how to run the Coverity suite locally.
Kumar Kartikeya Dwivedi (3):
libbpf: remove unneeded check for flags during detach
libbpf: set NLM_F_EXCL when creating qdisc
libbpf: add request buffer type for netlink messages
tools/lib/bpf/netlink.c | 111 +++++++++++++++-------------------------
tools/lib/bpf/nlattr.h | 37 +++++++++-----
2 files changed, 66 insertions(+), 82 deletions(-)
--
2.31.1
next reply other threads:[~2021-06-12 2:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-12 2:34 Kumar Kartikeya Dwivedi [this message]
2021-06-12 2:35 ` [PATCH bpf-next 1/3] libbpf: remove unneeded check for flags during detach Kumar Kartikeya Dwivedi
2021-06-12 2:35 ` [PATCH bpf-next 2/3] libbpf: set NLM_F_EXCL when creating qdisc Kumar Kartikeya Dwivedi
2021-06-12 2:35 ` [PATCH bpf-next 3/3] libbpf: add request buffer type for netlink messages Kumar Kartikeya Dwivedi
2021-06-15 12:23 ` Daniel Borkmann
2021-06-14 9:32 [PATCH bpf-next 0/3] Fixes for TC-BPF series Yaniv Agman
2021-06-14 10:18 ` Kumar Kartikeya Dwivedi
2021-06-14 11:08 ` Yaniv Agman
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=20210612023502.1283837-1-memxor@gmail.com \
--to=memxor@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=netdev@vger.kernel.org \
--cc=toke@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.