From: Song Liu <song@kernel.org>
To: <bpf@vger.kernel.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: <andrii@kernel.org>, <ast@kernel.org>, <daniel@iogearbox.net>,
<kernel-team@fb.com>, <hch@infradead.org>, <peterz@infradead.org>,
<torvalds@linux-foundation.org>, Song Liu <song@kernel.org>
Subject: [PATCH bpf v2 0/3] bpf: invalidate unused part of bpf_prog_pack
Date: Mon, 25 Apr 2022 13:39:44 -0700 [thread overview]
Message-ID: <20220425203947.3311308-1-song@kernel.org> (raw)
Note: while prefixed with "bpf", this set is based on Linus' master branch.
This is v2 of [1]. It is revised based on Peter's feedback. The patch is
also split into 3.
[1] https://lore.kernel.org/linux-mm/20220421072212.608884-1-song@kernel.org/
Song Liu (3):
bpf: fill new bpf_prog_pack with illegal instructions
x86/alternative: introduce text_poke_set
bpf: introduce bpf_arch_text_invalidate for bpf_prog_pack
arch/x86/include/asm/text-patching.h | 1 +
arch/x86/kernel/alternative.c | 70 ++++++++++++++++++++++++----
arch/x86/net/bpf_jit_comp.c | 5 ++
include/linux/bpf.h | 1 +
kernel/bpf/core.c | 18 +++++--
5 files changed, 81 insertions(+), 14 deletions(-)
--
2.30.2
next reply other threads:[~2022-04-25 20:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 20:39 Song Liu [this message]
2022-04-25 20:39 ` [PATCH v2 bpf 1/3] bpf: fill new bpf_prog_pack with illegal instructions Song Liu
2022-04-25 20:39 ` [PATCH v2 bpf 2/3] x86/alternative: introduce text_poke_set Song Liu
2022-04-25 20:39 ` [PATCH v2 bpf 3/3] bpf: introduce bpf_arch_text_invalidate for bpf_prog_pack Song Liu
2022-04-27 22:10 ` [PATCH bpf v2 0/3] bpf: invalidate unused part of bpf_prog_pack Song Liu
2022-04-28 1:45 ` Linus Torvalds
2022-04-28 6:48 ` Song Liu
2022-05-07 6:50 ` Song Liu
2022-05-07 19:36 ` Song Liu
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=20220425203947.3311308-1-song@kernel.org \
--to=song@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=hch@infradead.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
/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