From: Kui-Feng Lee <kuifeng@fb.com>
To: "alexei.starovoitov@gmail.com" <alexei.starovoitov@gmail.com>
Cc: "daniel@iogearbox.net" <daniel@iogearbox.net>,
Kernel Team <Kernel-team@fb.com>,
"ast@kernel.org" <ast@kernel.org>,
"andrii@kernel.org" <andrii@kernel.org>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>
Subject: Re: [PATCH bpf-next v7 2/5] bpf, x86: Create bpf_tramp_run_ctx on the caller thread's stack
Date: Tue, 10 May 2022 01:43:46 +0000 [thread overview]
Message-ID: <34dd81b7fe8f0e683a56a8fbcb32957d1d61969e.camel@fb.com> (raw)
In-Reply-To: <c3ade9c0ad19e9cef5864c0df948e0ae4cd54709.camel@fb.com>
On Tue, 2022-05-10 at 01:29 +0000, Kui-Feng Lee wrote:
> On Mon, 2022-05-09 at 14:04 -0700, Alexei Starovoitov wrote:
> > On Sat, May 07, 2022 at 08:21:14PM -0700, Kui-Feng Lee wrote:
> > >
> > > + /* Prepare struct bpf_tramp_run_ctx.
> > > + * sub rsp, sizeof(struct bpf_tramp_run_ctx)
> > > + */
> > > + EMIT4(0x48, 0x83, 0xEC, sizeof(struct
> > > bpf_tramp_run_ctx));
> > > +
> > > if (fentry->nr_links)
> > > if (invoke_bpf(m, &prog, fentry, regs_off,
> > > flags &
> > > BPF_TRAMP_F_RET_FENTRY_RET))
> > > @@ -2098,6 +2121,11 @@ int arch_prepare_bpf_trampoline(struct
> > > bpf_tramp_image *im, void *image, void *i
> > > }
> > >
> > > if (flags & BPF_TRAMP_F_CALL_ORIG) {
> > > + /* pop struct bpf_tramp_run_ctx
> > > + * add rsp, sizeof(struct bpf_tramp_run_ctx)
> > > + */
> > > + EMIT4(0x48, 0x83, 0xC4, sizeof(struct
> > > bpf_tramp_run_ctx));
> > > +
> > > restore_regs(m, &prog, nr_args, regs_off);
> > >
> > > /* call original function */
> > > @@ -2110,6 +2138,11 @@ int arch_prepare_bpf_trampoline(struct
> > > bpf_tramp_image *im, void *image, void *i
> > > im->ip_after_call = prog;
> > > memcpy(prog, x86_nops[5], X86_PATCH_SIZE);
> > > prog += X86_PATCH_SIZE;
> > > +
> > > + /* Prepare struct bpf_tramp_run_ctx.
> > > + * sub rsp, sizeof(struct bpf_tramp_run_ctx)
> > > + */
> > > + EMIT4(0x48, 0x83, 0xEC, sizeof(struct
> > > bpf_tramp_run_ctx));
> > > }
> > >
> > > if (fmod_ret->nr_links) {
> > > @@ -2133,6 +2166,11 @@ int arch_prepare_bpf_trampoline(struct
> > > bpf_tramp_image *im, void *image, void *i
> > > goto cleanup;
> > > }
> > >
> > > + /* pop struct bpf_tramp_run_ctx
> > > + * add rsp, sizeof(struct bpf_tramp_run_ctx)
> > > + */
> > > + EMIT4(0x48, 0x83, 0xC4, sizeof(struct
> > > bpf_tramp_run_ctx));
> > > +
> >
> > What is the point of all of these additional sub/add rsp ?
> > It seems unconditionally increasing stack_size by sizeof(struct
> > bpf_tramp_run_ctx)
> > will achieve the same and above 4 extra insns won't be needed.
>
> I think you are right.
>
The reason that I don't change stack_size is that we access arguments
or saved registers basing on stack_size. Once the stack_size is
changed, all these offsets should be changed too.
next prev parent reply other threads:[~2022-05-10 1:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-08 3:21 [PATCH bpf-next v7 0/5] Attach a cookie to a tracing program Kui-Feng Lee
2022-05-08 3:21 ` [PATCH bpf-next v7 1/5] bpf, x86: Generate trampolines from bpf_tramp_links Kui-Feng Lee
2022-05-09 18:54 ` Andrii Nakryiko
2022-05-10 16:50 ` Kui-Feng Lee
2022-05-08 3:21 ` [PATCH bpf-next v7 2/5] bpf, x86: Create bpf_tramp_run_ctx on the caller thread's stack Kui-Feng Lee
2022-05-09 18:54 ` Andrii Nakryiko
2022-05-09 21:04 ` Alexei Starovoitov
2022-05-10 1:29 ` Kui-Feng Lee
2022-05-10 1:43 ` Kui-Feng Lee [this message]
2022-05-10 2:11 ` Alexei Starovoitov
2022-05-08 3:21 ` [PATCH bpf-next v7 3/5] bpf, x86: Attach a cookie to fentry/fexit/fmod_ret/lsm Kui-Feng Lee
2022-05-09 18:58 ` Andrii Nakryiko
2022-05-10 16:44 ` Kui-Feng Lee
2022-05-10 18:44 ` Andrii Nakryiko
2022-05-08 3:21 ` [PATCH bpf-next v7 4/5] libbpf: Assign cookies to links in libbpf Kui-Feng Lee
2022-05-09 19:05 ` Andrii Nakryiko
2022-05-10 17:23 ` Kui-Feng Lee
2022-05-08 3:21 ` [PATCH bpf-next v7 5/5] selftest/bpf: The test cses of BPF cookie for fentry/fexit/fmod_ret/lsm Kui-Feng Lee
2022-05-09 19:08 ` Andrii Nakryiko
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=34dd81b7fe8f0e683a56a8fbcb32957d1d61969e.camel@fb.com \
--to=kuifeng@fb.com \
--cc=Kernel-team@fb.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
/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