From: Andrey Ignatov <rdna@fb.com>
To: <netdev@vger.kernel.org>
Cc: Andrey Ignatov <rdna@fb.com>, <ast@kernel.org>,
<daniel@iogearbox.net>, <kernel-team@fb.com>
Subject: [PATCH bpf-next 0/5] bpf: Fix indirect var_off stack access support
Date: Tue, 2 Apr 2019 13:19:54 -0700 [thread overview]
Message-ID: <cover.1554236245.git.rdna@fb.com> (raw)
This patch set is a follow-up for discussion [1].
It fixes variable offset stack access handling for raw and unprivileged
mode, rejecting both of them.
Patch 1 handles raw (uninitialized) mode.
Patch 2 adds test for raw mode.
Patch 3 handles unprivileged mode.
Patch 4 adds test for unprivileged mode.
Patch 5 is a minor fix in verbose log.
Unprivileged mode is an interesting case since one (and only?) way to come up
with variable offset is to use pointer arithmetics. Though pointer arithmetics
is already prohibited for unprivileged mode. I'm not sure if it's enough though
and it seems like a good idea to still reject variable offset for unpriv in
check_stack_boundary(). Please see patches 3 and 4 for more details on this.
[1] https://marc.info/?l=linux-netdev&m=155419526427742&w=2
Andrey Ignatov (5):
bpf: Reject indirect var_off stack access in raw mode
selftests/bpf: Test indirect var_off stack access in raw mode
bpf: Reject indirect var_off stack access in unpriv mode
selftests/bpf: Test indirect var_off stack access in unpriv mode
bpf: Add missed newline in verifier verbose log
kernel/bpf/verifier.c | 43 ++++++++++++---
.../testing/selftests/bpf/verifier/var_off.c | 54 +++++++++++++++++++
2 files changed, 90 insertions(+), 7 deletions(-)
--
2.17.1
next reply other threads:[~2019-04-02 20:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 20:19 Andrey Ignatov [this message]
2019-04-02 20:19 ` [PATCH bpf-next 1/5] bpf: Reject indirect var_off stack access in raw mode Andrey Ignatov
2019-04-03 16:21 ` Daniel Borkmann
2019-04-03 16:45 ` Daniel Borkmann
2019-04-03 21:57 ` Andrey Ignatov
2019-04-03 23:18 ` Daniel Borkmann
2019-04-04 1:02 ` Andrey Ignatov
2019-04-03 21:02 ` Andrey Ignatov
2019-04-03 22:31 ` Daniel Borkmann
2019-04-02 20:19 ` [PATCH bpf-next 2/5] selftests/bpf: Test " Andrey Ignatov
2019-04-02 20:19 ` [PATCH bpf-next 3/5] bpf: Reject indirect var_off stack access in unpriv mode Andrey Ignatov
2019-04-02 20:19 ` [PATCH bpf-next 4/5] selftests/bpf: Test " Andrey Ignatov
2019-04-02 20:19 ` [PATCH bpf-next 5/5] bpf: Add missed newline in verifier verbose log Andrey Ignatov
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=cover.1554236245.git.rdna@fb.com \
--to=rdna@fb.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).