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, roman.gushchin@linux.dev,
haoluo@google.com, shakeelb@google.com
Cc: bpf@vger.kernel.org, linux-mm@kvack.org,
Yafang Shao <laoar.shao@gmail.com>
Subject: [PATCH bpf-next v3 0/2] bpf: Minor fixes for non-preallocated memory
Date: Sat, 9 Jul 2022 15:44:55 +0000 [thread overview]
Message-ID: <20220709154457.57379-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/
v3:
- use GFP_NOWAIT instead and update commit log (Shakeel)
- exclude some attach types for BPF_PROG_TYPE_TRACING (Alexei)
v2:
- fix GFP_HIGH consistently over the bpf code. (Daniel, Roman)
- get rid of an error patch (Hao)
Yafang Shao (2):
bpf: Make non-preallocated allocation low priority
bpf: Warn on non-preallocated case for missed trace types
kernel/bpf/devmap.c | 2 +-
kernel/bpf/hashtab.c | 6 +++---
kernel/bpf/local_storage.c | 2 +-
kernel/bpf/lpm_trie.c | 2 +-
kernel/bpf/verifier.c | 18 +++++++++++++-----
5 files changed, 19 insertions(+), 11 deletions(-)
--
2.17.1
next reply other threads:[~2022-07-09 15:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 15:44 Yafang Shao [this message]
2022-07-09 15:44 ` [PATCH bpf-next v3 1/2] bpf: Make non-preallocated allocation low priority Yafang Shao
2022-07-11 19:19 ` Shakeel Butt
2022-07-13 0:49 ` Alexei Starovoitov
2022-07-13 2:12 ` Roman Gushchin
2022-07-09 15:44 ` [PATCH bpf-next v3 2/2] bpf: Warn on non-preallocated case for missed trace types Yafang Shao
2022-07-10 17:51 ` Yonghong Song
2022-07-11 6:48 ` Yafang Shao
2022-07-11 19:04 ` Yonghong Song
2022-07-12 8:26 ` Yafang Shao
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=20220709154457.57379-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=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-mm@kvack.org \
--cc=quentin@isovalent.com \
--cc=roman.gushchin@linux.dev \
--cc=shakeelb@google.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 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).