From: dthaler1968@googlemail.com
To: "'Alexei Starovoitov'" <alexei.starovoitov@gmail.com>,
<bpf@vger.kernel.org>
Cc: <daniel@iogearbox.net>, <andrii@kernel.org>,
<martin.lau@kernel.org>, <memxor@gmail.com>, <eddyz87@gmail.com>,
<john.fastabend@gmail.com>, <kernel-team@fb.com>, <bpf@ietf.org>
Subject: RE: [PATCH v4 bpf-next 0/4] bpf: Introduce may_goto and cond_break
Date: Mon, 4 Mar 2024 08:45:38 -0800 [thread overview]
Message-ID: <270f01da6e53$63e93620$2bbba260$@gmail.com> (raw)
In-Reply-To: <20240302020010.95393-1-alexei.starovoitov@gmail.com>
Alexei Starovoitov <alexei.starovoitov@gmail.com> writes:
[...]
> Alexei Starovoitov (4):
> bpf: Introduce may_goto instruction
> bpf: Recognize that two registers are safe when their ranges match
> bpf: Add cond_break macro
> selftests/bpf: Test may_goto
>
> include/linux/bpf_verifier.h | 2 +
> include/uapi/linux/bpf.h | 1 +
> kernel/bpf/core.c | 1 +
> kernel/bpf/disasm.c | 3 +
> kernel/bpf/verifier.c | 280 +++++++++++++-----
> tools/include/uapi/linux/bpf.h | 1 +
> tools/testing/selftests/bpf/DENYLIST.s390x | 1 +
> .../testing/selftests/bpf/bpf_experimental.h | 12 +
> .../bpf/progs/verifier_iterating_callbacks.c | 103 ++++++-
> 9 files changed, 330 insertions(+), 74 deletions(-)
Don't we also need to add may_goto to instruction-set.rst?
Dave
WARNING: multiple messages have this Message-ID (diff)
From: dthaler1968=40googlemail.com@dmarc.ietf.org
To: "'Alexei Starovoitov'" <alexei.starovoitov@gmail.com>,
<bpf@vger.kernel.org>
Cc: <daniel@iogearbox.net>, <andrii@kernel.org>,
<martin.lau@kernel.org>, <memxor@gmail.com>, <eddyz87@gmail.com>,
<john.fastabend@gmail.com>, <kernel-team@fb.com>, <bpf@ietf.org>
Subject: Re: [Bpf] [PATCH v4 bpf-next 0/4] bpf: Introduce may_goto and cond_break
Date: Mon, 4 Mar 2024 08:45:38 -0800 [thread overview]
Message-ID: <270f01da6e53$63e93620$2bbba260$@gmail.com> (raw)
Message-ID: <20240304164538.GGqddTnXdkAF0LC9vt4zfOS_O4-vWNWmVSqaU_KQ-8s@z> (raw)
In-Reply-To: <20240302020010.95393-1-alexei.starovoitov@gmail.com>
Alexei Starovoitov <alexei.starovoitov@gmail.com> writes:
[...]
> Alexei Starovoitov (4):
> bpf: Introduce may_goto instruction
> bpf: Recognize that two registers are safe when their ranges match
> bpf: Add cond_break macro
> selftests/bpf: Test may_goto
>
> include/linux/bpf_verifier.h | 2 +
> include/uapi/linux/bpf.h | 1 +
> kernel/bpf/core.c | 1 +
> kernel/bpf/disasm.c | 3 +
> kernel/bpf/verifier.c | 280 +++++++++++++-----
> tools/include/uapi/linux/bpf.h | 1 +
> tools/testing/selftests/bpf/DENYLIST.s390x | 1 +
> .../testing/selftests/bpf/bpf_experimental.h | 12 +
> .../bpf/progs/verifier_iterating_callbacks.c | 103 ++++++-
> 9 files changed, 330 insertions(+), 74 deletions(-)
Don't we also need to add may_goto to instruction-set.rst?
Dave
--
Bpf mailing list
Bpf@ietf.org
https://www.ietf.org/mailman/listinfo/bpf
next prev parent reply other threads:[~2024-03-04 16:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-02 2:00 [PATCH v4 bpf-next 0/4] bpf: Introduce may_goto and cond_break Alexei Starovoitov
2024-03-02 2:00 ` [PATCH v4 bpf-next 1/4] bpf: Introduce may_goto instruction Alexei Starovoitov
2024-03-04 11:55 ` Eduard Zingerman
2024-03-04 16:59 ` Alexei Starovoitov
2024-03-02 2:00 ` [PATCH v4 bpf-next 2/4] bpf: Recognize that two registers are safe when their ranges match Alexei Starovoitov
2024-03-03 14:12 ` Eduard Zingerman
2024-03-03 17:21 ` Alexei Starovoitov
2024-03-05 3:44 ` Alexei Starovoitov
2024-03-02 2:00 ` [PATCH v4 bpf-next 3/4] bpf: Add cond_break macro Alexei Starovoitov
2024-03-02 2:00 ` [PATCH v4 bpf-next 4/4] selftests/bpf: Test may_goto Alexei Starovoitov
2024-03-04 16:45 ` dthaler1968 [this message]
2024-03-04 16:45 ` [Bpf] [PATCH v4 bpf-next 0/4] bpf: Introduce may_goto and cond_break dthaler1968=40googlemail.com
2024-03-04 17:05 ` Alexei Starovoitov
2024-03-04 17:05 ` [Bpf] " Alexei Starovoitov
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='270f01da6e53$63e93620$2bbba260$@gmail.com' \
--to=dthaler1968@googlemail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@ietf.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=john.fastabend@gmail.com \
--cc=kernel-team@fb.com \
--cc=martin.lau@kernel.org \
--cc=memxor@gmail.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