From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Song Liu <songliubraving@fb.com>
Cc: "David S . Miller" <davem@davemloft.net>,
Daniel Borkmann <daniel@iogearbox.net>,
Networking <netdev@vger.kernel.org>, bpf <bpf@vger.kernel.org>,
Kernel Team <Kernel-team@fb.com>
Subject: Re: [PATCH bpf-next] bpf: Emit explicit NULL pointer checks for PROBE_LDX instructions.
Date: Tue, 2 Feb 2021 18:19:15 -0800 [thread overview]
Message-ID: <20210203021915.5cfdrt3wwmskopuw@ast-mbp.dhcp.thefacebook.com> (raw)
In-Reply-To: <A746402C-245A-4FF1-AB54-585537EEBA9B@fb.com>
On Wed, Feb 03, 2021 at 12:56:39AM +0000, Song Liu wrote:
>
>
> > On Feb 1, 2021, at 9:38 PM, Alexei Starovoitov <alexei.starovoitov@gmail.com> wrote:
> >
> > From: Alexei Starovoitov <ast@kernel.org>
> >
> > PTR_TO_BTF_ID registers contain either kernel pointer or NULL.
> > Emit the NULL check explicitly by JIT instead of going into
> > do_user_addr_fault() on NULL deference.
> >
> > Signed-off-by: Alexei Starovoitov <ast@kernel.org>
> > ---
> > arch/x86/net/bpf_jit_comp.c | 19 +++++++++++++++++++
> > 1 file changed, 19 insertions(+)
> >
> > diff --git a/arch/x86/net/bpf_jit_comp.c b/arch/x86/net/bpf_jit_comp.c
> > index b7a2911bda77..a3dc3bd154ac 100644
> > --- a/arch/x86/net/bpf_jit_comp.c
> > +++ b/arch/x86/net/bpf_jit_comp.c
> > @@ -930,6 +930,7 @@ static int do_jit(struct bpf_prog *bpf_prog, int *addrs, u8 *image,
> > u32 dst_reg = insn->dst_reg;
> > u32 src_reg = insn->src_reg;
> > u8 b2 = 0, b3 = 0;
> > + u8 *start_of_ldx;
> > s64 jmp_offset;
> > u8 jmp_cond;
> > u8 *func;
> > @@ -1278,12 +1279,30 @@ st: if (is_imm8(insn->off))
> > case BPF_LDX | BPF_PROBE_MEM | BPF_W:
> > case BPF_LDX | BPF_MEM | BPF_DW:
> > case BPF_LDX | BPF_PROBE_MEM | BPF_DW:
> > + if (BPF_MODE(insn->code) == BPF_PROBE_MEM) {
> > + /* test src_reg, src_reg */
> > + maybe_emit_mod(&prog, src_reg, src_reg, true); /* always 1 byte */
> > + EMIT2(0x85, add_2reg(0xC0, src_reg, src_reg));
> > + /* jne start_of_ldx */
> > + EMIT2(X86_JNE, 0);
> > + /* xor dst_reg, dst_reg */
> > + emit_mov_imm32(&prog, false, dst_reg, 0);
> > + /* jmp byte_after_ldx */
> > + EMIT2(0xEB, 0);
> > +
> > + /* populate jmp_offset for JNE above */
> > + temp[4] = prog - temp - 5 /* sizeof(test + jne) */;
>
> IIUC, this case only happens for i == 1 in the loop? If so, can we use temp[5(?)]
> instead of start_of_ldx?
I don't understand the question, but let me try anyway :)
temp is a buffer for single instruction.
prog=temp; for every loop iteration (not only i == 1)
temp[4] is second byte in JNE instruction as the comment says.
temp[5] is a byte after JNE. It's a first byte of XOR.
That XOR is variable length instruction.
Hence while emitting JNE we don't know the target offset in JNE and just use 0.
So temp[4] assignment populates with actual offset, since now we know the size
of XOR.
next prev parent reply other threads:[~2021-02-03 2:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 5:38 [PATCH bpf-next] bpf: Emit explicit NULL pointer checks for PROBE_LDX instructions Alexei Starovoitov
2021-02-03 0:56 ` Song Liu
2021-02-03 2:19 ` Alexei Starovoitov [this message]
2021-02-03 18:37 ` Song Liu
2021-02-04 16:10 ` patchwork-bot+netdevbpf
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=20210203021915.5cfdrt3wwmskopuw@ast-mbp.dhcp.thefacebook.com \
--to=alexei.starovoitov@gmail.com \
--cc=Kernel-team@fb.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@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;
as well as URLs for NNTP newsgroup(s).