From: Yafang Shao <laoar.shao@gmail.com>
To: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org,
quentin@isovalent.com
Cc: netdev@vger.kernel.org, bpf@vger.kernel.org,
Yafang Shao <laoar.shao@gmail.com>
Subject: [PATCH bpf-next 0/4] bpf: Minor fixes
Date: Wed, 29 Jun 2022 15:48:28 +0000 [thread overview]
Message-ID: <20220629154832.56986-1-laoar.shao@gmail.com> (raw)
When I was implementing bpf recharge[1], I found some other issues.
These issues are independent, so I send them separately.
[1]. https://lore.kernel.org/bpf/20220619155032.32515-1-laoar.shao@gmail.com/
Yafang Shao (4):
bpf: Make non-preallocated allocation low priority
bpf: Warn on non-preallocated case for missed trace types
bpf: Don't do preempt check when migrate is disabled
bpftool: Show also the name of type BPF_OBJ_LINK
kernel/bpf/bpf_task_storage.c | 8 ++++----
kernel/bpf/hashtab.c | 14 ++++++++------
kernel/bpf/trampoline.c | 4 ++--
kernel/bpf/verifier.c | 2 ++
tools/bpf/bpftool/common.c | 1 +
5 files changed, 17 insertions(+), 12 deletions(-)
--
2.17.1
next reply other threads:[~2022-06-29 15:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 15:48 Yafang Shao [this message]
2022-06-29 15:48 ` [PATCH bpf-next 1/4] bpf: Make non-preallocated allocation low priority Yafang Shao
2022-06-30 21:47 ` Daniel Borkmann
2022-07-02 2:30 ` Yafang Shao
2022-07-02 4:14 ` Roman Gushchin
2022-07-02 15:08 ` Yafang Shao
2022-07-02 3:54 ` Roman Gushchin
2022-06-29 15:48 ` [PATCH bpf-next 2/4] bpf: Warn on non-preallocated case for missed trace types Yafang Shao
2022-06-29 15:48 ` [PATCH bpf-next 3/4] bpf: Don't do preempt check when migrate is disabled Yafang Shao
2022-06-30 20:43 ` Hao Luo
2022-07-02 2:34 ` Yafang Shao
2022-06-29 15:48 ` [PATCH bpf-next 4/4] bpftool: Show also the name of type BPF_OBJ_LINK Yafang Shao
2022-06-29 16:22 ` Quentin Monnet
2022-06-30 21:55 ` Daniel Borkmann
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=20220629154832.56986-1-laoar.shao@gmail.com \
--to=laoar.shao@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=quentin@isovalent.com \
--cc=songliubraving@fb.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 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.