From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Martin KaFai Lau <kafai@fb.com>, bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
David Miller <davem@davemloft.net>,
kernel-team@fb.com, netdev@vger.kernel.org
Subject: Re: [PATCH bpf-next v4 01/11] bpf: Save PTR_TO_BTF_ID register state when spilling to stack
Date: Wed, 08 Jan 2020 22:06:44 -0300 [thread overview]
Message-ID: <9EC7DCC9-B219-4545-BA93-E2AC0569C843@kernel.org> (raw)
In-Reply-To: <20200109004424.3894196-1-kafai@fb.com>
On January 8, 2020 9:44:24 PM GMT-03:00, Martin KaFai Lau <kafai@fb.com> wrote:
>This patch makes the verifier save the PTR_TO_BTF_ID register state
>when
>spilling to the stack.
You say what it does, but not why that is needed :-/
- Arnaldo
>
>Acked-by: Yonghong Song <yhs@fb.com>
>Signed-off-by: Martin KaFai Lau <kafai@fb.com>
>---
> kernel/bpf/verifier.c | 1 +
> 1 file changed, 1 insertion(+)
>
>diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
>index 6f63ae7a370c..d433d70022fd 100644
>--- a/kernel/bpf/verifier.c
>+++ b/kernel/bpf/verifier.c
>@@ -1916,6 +1916,7 @@ static bool is_spillable_regtype(enum
>bpf_reg_type type)
> case PTR_TO_TCP_SOCK:
> case PTR_TO_TCP_SOCK_OR_NULL:
> case PTR_TO_XDP_SOCK:
>+ case PTR_TO_BTF_ID:
> return true;
> default:
> return false;
next prev parent reply other threads:[~2020-01-09 1:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 0:34 [PATCH bpf-next v4 00/11] Introduce BPF STRUCT_OPS Martin KaFai Lau
2020-01-09 0:34 ` [PATCH bpf-next v4 01/11] bpf: Save PTR_TO_BTF_ID register state when spilling to stack Martin KaFai Lau
2020-01-09 0:34 ` [PATCH bpf-next v4 02/11] bpf: Avoid storing modifier to info->btf_id Martin KaFai Lau
2020-01-09 0:34 ` [PATCH bpf-next v4 03/11] bpf: Add enum support to btf_ctx_access() Martin KaFai Lau
2020-01-09 0:35 ` [PATCH bpf-next v4 04/11] bpf: Support bitfield read access in btf_struct_access Martin KaFai Lau
2020-01-09 0:35 ` [PATCH bpf-next v4 05/11] bpf: Introduce BPF_PROG_TYPE_STRUCT_OPS Martin KaFai Lau
2020-01-09 0:35 ` [PATCH bpf-next v4 06/11] bpf: Introduce BPF_MAP_TYPE_STRUCT_OPS Martin KaFai Lau
2020-01-09 0:35 ` [PATCH bpf-next v4 07/11] bpf: tcp: Support tcp_congestion_ops in bpf Martin KaFai Lau
2020-01-09 0:35 ` [PATCH bpf-next v4 08/11] bpf: Add BPF_FUNC_tcp_send_ack helper Martin KaFai Lau
2020-01-09 0:35 ` [PATCH bpf-next v4 09/11] bpf: Synch uapi bpf.h to tools/ Martin KaFai Lau
2020-01-09 0:35 ` [PATCH bpf-next v4 10/11] bpf: libbpf: Add STRUCT_OPS support Martin KaFai Lau
2020-01-09 0:35 ` [PATCH bpf-next v4 11/11] bpf: Add bpf_dctcp example Martin KaFai Lau
2020-01-09 0:44 ` [PATCH bpf-next v4 01/11] bpf: Save PTR_TO_BTF_ID register state when spilling to stack Martin KaFai Lau
2020-01-09 1:06 ` Arnaldo Carvalho de Melo [this message]
2020-01-09 5:47 ` Martin Lau
2020-01-09 13:23 ` Arnaldo Carvalho de Melo
2020-01-09 0:45 ` [PATCH bpf-next v4 08/11] bpf: Add BPF_FUNC_tcp_send_ack helper Martin KaFai Lau
2020-01-09 17:52 ` [PATCH bpf-next v4 00/11] Introduce BPF STRUCT_OPS Alexei Starovoitov
2020-01-09 22:36 ` 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=9EC7DCC9-B219-4545-BA93-E2AC0569C843@kernel.org \
--to=arnaldo.melo@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=kafai@fb.com \
--cc=kernel-team@fb.com \
--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;
as well as URLs for NNTP newsgroup(s).