From: Kumar Kartikeya Dwivedi <memxor@gmail.com>
To: bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>
Subject: [PATCH bpf v2 0/3] Fixes for kfunc-mod regressions and warnings
Date: Mon, 22 Nov 2021 20:17:39 +0530 [thread overview]
Message-ID: <20211122144742.477787-1-memxor@gmail.com> (raw)
This set includes fixes for two regressions and one build warning introduced by
the kfunc for modules series.
Changelog:
----------
v1 -> v2:
v1: https://lore.kernel.org/bpf/20211115191840.496263-1-memxor@gmail.com
* Instead of demoting resolve_btfids warning to debug, only skip in case of
set->cnt == 0.
Kumar Kartikeya Dwivedi (3):
bpf: Make CONFIG_DEBUG_INFO_BTF depend upon CONFIG_BPF_SYSCALL
bpf: Fix bpf_check_mod_kfunc_call for built-in modules
tools/resolve_btfids: Skip unresolved symbol warning for empty BTF
sets
include/linux/btf.h | 14 ++++++++++----
kernel/bpf/btf.c | 11 ++---------
lib/Kconfig.debug | 1 +
tools/bpf/resolve_btfids/main.c | 8 +++++---
4 files changed, 18 insertions(+), 16 deletions(-)
--
2.34.0
next reply other threads:[~2021-11-22 14:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 14:47 Kumar Kartikeya Dwivedi [this message]
2021-11-22 14:47 ` [PATCH bpf v2 1/3] bpf: Make CONFIG_DEBUG_INFO_BTF depend upon CONFIG_BPF_SYSCALL Kumar Kartikeya Dwivedi
2021-11-26 7:06 ` Song Liu
2025-05-14 10:30 ` Geert Uytterhoeven
2021-11-22 14:47 ` [PATCH bpf v2 2/3] bpf: Fix bpf_check_mod_kfunc_call for built-in modules Kumar Kartikeya Dwivedi
2021-11-26 7:13 ` Song Liu
2021-11-22 14:47 ` [PATCH bpf v2 3/3] tools/resolve_btfids: Skip unresolved symbol warning for empty BTF sets Kumar Kartikeya Dwivedi
2021-11-26 7:37 ` Song Liu
2021-11-29 23:46 ` Andrii Nakryiko
2021-11-30 19:56 ` Kumar Kartikeya Dwivedi
2021-12-02 22:39 ` Andrii Nakryiko
2021-12-02 22:30 ` [PATCH bpf v2 0/3] Fixes for kfunc-mod regressions and warnings 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=20211122144742.477787-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 \
/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;
as well as URLs for NNTP newsgroup(s).