From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Joe Stringer <joe@wand.net.nz>
Cc: daniel@iogearbox.net, netdev@vger.kernel.org, ast@kernel.org,
john.fastabend@gmail.com, tgraf@suug.ch, kafai@fb.com,
nitin.hande@gmail.com, mauricio.vasquez@polito.it
Subject: Re: [PATCH bpf-next 05/11] bpf: Macrofy stack state copy
Date: Wed, 12 Sep 2018 15:51:43 -0700 [thread overview]
Message-ID: <20180912225141.ommigjidpoiwixew@ast-mbp> (raw)
In-Reply-To: <20180912003640.28316-6-joe@wand.net.nz>
On Tue, Sep 11, 2018 at 05:36:34PM -0700, Joe Stringer wrote:
> An upcoming commit will need very similar copy/realloc boilerplate, so
> refactor the existing stack copy/realloc functions into macros to
> simplify it.
>
> Signed-off-by: Joe Stringer <joe@wand.net.nz>
Acked-by: Alexei Starovoitov <ast@kernel.org>
next prev parent reply other threads:[~2018-09-13 3:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 0:36 [PATCH bpf-next 00/11] Add socket lookup support Joe Stringer
2018-09-12 0:36 ` [PATCH bpf-next 01/11] bpf: Add iterator for spilled registers Joe Stringer
2018-09-12 0:36 ` [PATCH bpf-next 02/11] bpf: Simplify ptr_min_max_vals adjustment Joe Stringer
2018-09-12 0:36 ` [PATCH bpf-next 03/11] bpf: Generalize ptr_or_null regs check Joe Stringer
2018-09-12 0:36 ` [PATCH bpf-next 04/11] bpf: Add PTR_TO_SOCKET verifier type Joe Stringer
2018-09-12 22:50 ` Alexei Starovoitov
2018-09-13 18:59 ` Joe Stringer
2018-09-12 0:36 ` [PATCH bpf-next 05/11] bpf: Macrofy stack state copy Joe Stringer
2018-09-12 22:51 ` Alexei Starovoitov [this message]
2018-09-12 0:36 ` [PATCH bpf-next 06/11] bpf: Add reference tracking to verifier Joe Stringer
2018-09-12 23:17 ` Alexei Starovoitov
2018-09-13 19:00 ` Joe Stringer
2018-09-12 0:36 ` [PATCH bpf-next 07/11] bpf: Add helper to retrieve socket in BPF Joe Stringer
2018-09-13 0:06 ` Alexei Starovoitov
2018-09-14 6:57 ` kbuild test robot
2018-09-14 7:11 ` kbuild test robot
2018-09-12 0:36 ` [PATCH bpf-next 08/11] selftests/bpf: Add tests for reference tracking Joe Stringer
2018-09-13 0:09 ` Alexei Starovoitov
2018-09-12 0:36 ` [PATCH bpf-next 09/11] libbpf: Support loading individual progs Joe Stringer
2018-09-13 0:10 ` Alexei Starovoitov
2018-09-12 0:36 ` [PATCH bpf-next 10/11] selftests/bpf: Add C tests for reference tracking Joe Stringer
2018-09-13 0:11 ` Alexei Starovoitov
2018-09-13 20:56 ` Joe Stringer
2018-09-12 0:36 ` [PATCH bpf-next 11/11] Documentation: Describe bpf " Joe Stringer
2018-09-13 0:12 ` Alexei Starovoitov
2018-09-13 20:56 ` Joe Stringer
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=20180912225141.ommigjidpoiwixew@ast-mbp \
--to=alexei.starovoitov@gmail.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=joe@wand.net.nz \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=mauricio.vasquez@polito.it \
--cc=netdev@vger.kernel.org \
--cc=nitin.hande@gmail.com \
--cc=tgraf@suug.ch \
/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