From: Alexei Starovoitov <ast@kernel.org>
To: Alex Gartrell <agartrell@fb.com>
Cc: daniel@iogearbox.net, netdev@vger.kernel.org, kernel-team@fb.com
Subject: Re: [RFC PATCH net-next] ebpf: Allow dereferences of PTR_TO_STACK registers
Date: Tue, 21 Jul 2015 20:00:48 -0700 [thread overview]
Message-ID: <20150722030047.GA14620@ast-dev1> (raw)
In-Reply-To: <1437530440-1474680-1-git-send-email-agartrell@fb.com>
On Tue, Jul 21, 2015 at 07:00:40PM -0700, Alex Gartrell wrote:
> mov %rsp, %r1 ; r1 = rsp
> add $-8, %r1 ; r1 = rsp - 8
> store_q $123, -8(%rsp) ; *(u64*)r1 = 123 <- valid
> store_q $123, (%r1) ; *(u64*)r1 = 123 <- previously invalid
> mov $0, %r0
> exit ; Always need to exit
Is this your new eBPF assembler syntax? :)
imo gnu style looks ugly... ;)
It's great to see such in-depth understanding of verifier!!
> And we'd get the following error:
>
> 0: (bf) r1 = r10
> 1: (07) r1 += -8
> 2: (7a) *(u64 *)(r10 -8) = 999
> 3: (7a) *(u64 *)(r1 +0) = 999
> R1 invalid mem access 'fp'
>
> Unable to load program
>
> We already know that a register is a stack address and the appropriate
> offset, so we should be able to validate those references as well.
yes, we can teach verifier to do that.
Though llvm doesn't generate such code. It's small enough change.
> Signed-off-by: Alex Gartrell <agartrell@fb.com>
> ---
> kernel/bpf/verifier.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
> index 039d866..5dfbece 100644
> --- a/kernel/bpf/verifier.c
> +++ b/kernel/bpf/verifier.c
> @@ -676,6 +676,15 @@ static int check_mem_access(struct verifier_env *env, u32 regno, int off,
> err = check_stack_write(state, off, size, value_regno);
> else
> err = check_stack_read(state, off, size, value_regno);
> + } else if (state->regs[regno].type == PTR_TO_STACK) {
> + int real_off = state->regs[regno].imm + off;
real_off is missing alignment and bounds checks.
something like:
if (state->regs[regno].type == PTR_TO_STACK)
off += state->regs[regno].imm;
if (off % size != 0)
...
else if (state->regs[regno].type == FRAME_PTR || == PTR_TO_STACK)
.. as-is here ...
would fix it.
please add few accept and reject tests for this to test_verifier.c as well.
next prev parent reply other threads:[~2015-07-22 3:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 2:00 [RFC PATCH net-next] ebpf: Allow dereferences of PTR_TO_STACK registers Alex Gartrell
2015-07-22 3:00 ` Alexei Starovoitov [this message]
2015-07-22 7:18 ` Alex Gartrell
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=20150722030047.GA14620@ast-dev1 \
--to=ast@kernel.org \
--cc=agartrell@fb.com \
--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).