From: Edward Cree <ecree@solarflare.com>
To: <daniel@iogearbox.net>, <ast@kernel.org>
Cc: <netdev@vger.kernel.org>
Subject: [PATCH bpf-next] bpf/verifier: properly clear union members after a ctx read
Date: Tue, 4 Sep 2018 15:19:52 +0100 [thread overview]
Message-ID: <0b724ba4-9ddf-e635-0bd5-201658355cf5@solarflare.com> (raw)
In check_mem_access(), for the PTR_TO_CTX case, after check_ctx_access()
has supplied a reg_type, the other members of the register state are set
appropriately. Previously reg.range was set to 0, but as it is in a
union with reg.map_ptr, which is larger, upper bytes of the latter were
left in place. This then caused the memcmp() in regsafe() to fail,
preventing some branches from being pruned (and occasionally causing the
same program to take a varying number of processed insns on repeated
verifier runs).
Signed-off-by: Edward Cree <ecree@solarflare.com>
---
Possibly something might need adding to __mark_reg_unknown() as well to
clear map_ptr/range, I'm not sure (though doing so did not affect the
processed insn count on the cilium programs).
kernel/bpf/verifier.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
index f4ff0c569e54..49e4ea66fdd3 100644
--- a/kernel/bpf/verifier.c
+++ b/kernel/bpf/verifier.c
@@ -1640,9 +1640,9 @@ static int check_mem_access(struct bpf_verifier_env *env, int insn_idx, u32 regn
else
mark_reg_known_zero(env, regs,
value_regno);
- regs[value_regno].id = 0;
- regs[value_regno].off = 0;
- regs[value_regno].range = 0;
+ /* Clear id, off, and union(map_ptr, range) */
+ memset(regs + value_regno, 0,
+ offsetof(struct bpf_reg_state, var_off));
regs[value_regno].type = reg_type;
}
next reply other threads:[~2018-09-04 18:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 14:19 Edward Cree [this message]
2018-09-05 2:23 ` [PATCH bpf-next] bpf/verifier: properly clear union members after a ctx read Alexei Starovoitov
2018-09-05 13:47 ` Edward Cree
2018-09-06 5:32 ` Alexei Starovoitov
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=0b724ba4-9ddf-e635-0bd5-201658355cf5@solarflare.com \
--to=ecree@solarflare.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--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