From: Yonghong Song <yhs@fb.com>
To: John Fastabend <john.fastabend@gmail.com>,
Eduard Zingerman <eddyz87@gmail.com>,
bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kernel-team@fb.com
Subject: Re: [PATCH RFC bpf-next 1/2] bpf: propagate nullness information for reg to reg comparisons
Date: Wed, 24 Aug 2022 19:55:51 -0700 [thread overview]
Message-ID: <d9bf2adc-96e6-c6cd-8d69-e381e8568e0b@fb.com> (raw)
In-Reply-To: <63055fa5a080e_292a8208db@john.notmuch>
On 8/23/22 4:15 PM, John Fastabend wrote:
> Eduard Zingerman wrote:
>> Propagate nullness information for branches of register to register
>> equality compare instructions. The following rules are used:
>> - suppose register A maybe null
>> - suppose register B is not null
>> - for JNE A, B, ... - A is not null in the false branch
>> - for JEQ A, B, ... - A is not null in the true branch
>>
>> E.g. for program like below:
>>
>> r6 = skb->sk;
>> r7 = sk_fullsock(r6);
>> r0 = sk_fullsock(r6);
>> if (r0 == 0) return 0; (a)
>> if (r0 != r7) return 0; (b)
>> *r7->type; (c)
>> return 0;
>>
>> It is safe to dereference r7 at point (c), because of (a) and (b).
>
> I think the idea makes sense. Perhaps Yonhong can comment seeing he was active
> on the LLVM thread. I just scanned the LLVM side for now will take a look
> in more detail in a bit.
The issue is discovered when making some changes in llvm compiler.
I think it is good to add support in verifier so in the future
if compiler generates such code patterns, user won't get
surprised verification failure.
>
>>
>> Signed-off-by: Eduard Zingerman <eddyz87@gmail.com>
>> ---
>> kernel/bpf/verifier.c | 39 ++++++++++++++++++++++++++++++++++++++-
>> 1 file changed, 38 insertions(+), 1 deletion(-)
>>
>> diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
>> index 2c1f8069f7b7..c48d34625bfd 100644
>> --- a/kernel/bpf/verifier.c
>> +++ b/kernel/bpf/verifier.c
>> @@ -472,6 +472,11 @@ static bool type_may_be_null(u32 type)
>> return type & PTR_MAYBE_NULL;
>> }
>>
>> +static bool type_is_pointer(enum bpf_reg_type type)
>> +{
>> + return type != NOT_INIT && type != SCALAR_VALUE;
>> +}
>> +
>
> Instead of having another helper is_pointer_value() could work here?
> Checking if we need NOT_INIT in that helper now.
>
>> static bool is_acquire_function(enum bpf_func_id func_id,
>> const struct bpf_map *map)
>> {
>> @@ -10046,6 +10051,7 @@ static int check_cond_jmp_op(struct bpf_verifier_env *env,
>> struct bpf_verifier_state *other_branch;
>> struct bpf_reg_state *regs = this_branch->frame[this_branch->curframe]->regs;
>> struct bpf_reg_state *dst_reg, *other_branch_regs, *src_reg = NULL;
>> + struct bpf_reg_state *eq_branch_regs;
>> u8 opcode = BPF_OP(insn->code);
>> bool is_jmp32;
>> int pred = -1;
>> @@ -10155,7 +10161,7 @@ static int check_cond_jmp_op(struct bpf_verifier_env *env,
>> /* detect if we are comparing against a constant value so we can adjust
>> * our min/max values for our dst register.
>> * this is only legit if both are scalars (or pointers to the same
>> - * object, I suppose, but we don't support that right now), because
>> + * object, I suppose, see the next if block), because
>> * otherwise the different base pointers mean the offsets aren't
>> * comparable.
>> */
>> @@ -10199,6 +10205,37 @@ static int check_cond_jmp_op(struct bpf_verifier_env *env,
>> opcode, is_jmp32);
>> }
>>
>> + /* if one pointer register is compared to another pointer
>> + * register check if PTR_MAYBE_NULL could be lifted.
>> + * E.g. register A - maybe null
>> + * register B - not null
>> + * for JNE A, B, ... - A is not null in the false branch;
>> + * for JEQ A, B, ... - A is not null in the true branch.
>> + */
>> + if (!is_jmp32 &&
>> + BPF_SRC(insn->code) == BPF_X &&
>> + type_is_pointer(src_reg->type) && type_is_pointer(dst_reg->type) &&
>> + type_may_be_null(src_reg->type) != type_may_be_null(dst_reg->type)) {
>> + eq_branch_regs = NULL;
>> + switch (opcode) {
>> + case BPF_JEQ:
>> + eq_branch_regs = other_branch_regs;
>> + break;
>> + case BPF_JNE:
>> + eq_branch_regs = regs;
>> + break;
>> + default:
>> + /* do nothing */
>> + break;
>> + }
>> + if (eq_branch_regs) {
>> + if (type_may_be_null(src_reg->type))
>> + mark_ptr_not_null_reg(&eq_branch_regs[insn->src_reg]);
>> + else
>> + mark_ptr_not_null_reg(&eq_branch_regs[insn->dst_reg]);
>> + }
>> + }
>> +
>> if (dst_reg->type == SCALAR_VALUE && dst_reg->id &&
>> !WARN_ON_ONCE(dst_reg->id != other_branch_regs[insn->dst_reg].id)) {
>> find_equal_scalars(this_branch, dst_reg);
>> --
>> 2.37.1
>>
>
>
next prev parent reply other threads:[~2022-08-25 2:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 9:43 [PATCH RFC bpf-next 0/2] propagate nullness information for reg to reg comparisons Eduard Zingerman
2022-08-22 9:43 ` [PATCH RFC bpf-next 1/2] bpf: " Eduard Zingerman
2022-08-23 23:15 ` John Fastabend
2022-08-24 22:05 ` Eduard Zingerman
2022-08-25 6:21 ` John Fastabend
2022-08-25 22:31 ` Eduard Zingerman
2022-08-25 2:55 ` Yonghong Song [this message]
2022-08-25 6:19 ` John Fastabend
2022-08-25 2:34 ` Yonghong Song
2022-08-22 9:43 ` [PATCH RFC bpf-next 2/2] selftests/bpf: check nullness propagation " Eduard Zingerman
2022-08-25 2:38 ` Yonghong Song
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=d9bf2adc-96e6-c6cd-8d69-e381e8568e0b@fb.com \
--to=yhs@fb.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=john.fastabend@gmail.com \
--cc=kernel-team@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