From: Eduard Zingerman <eddyz87@gmail.com>
To: Andrii Nakryiko <andrii@kernel.org>,
bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
martin.lau@kernel.org
Cc: kernel-team@meta.com, Hao Sun <sunhao.th@gmail.com>
Subject: Re: [PATCH bpf-next 4/4] selftests/bpf: add more test cases for check_cfg()
Date: Fri, 10 Nov 2023 00:21:38 +0200 [thread overview]
Message-ID: <3e8f251498ecaac279b3e60e0f37716c3c5fa34b.camel@gmail.com> (raw)
In-Reply-To: <20231108231152.3583545-5-andrii@kernel.org>
On Wed, 2023-11-08 at 15:11 -0800, Andrii Nakryiko wrote:
> Add a few more simple cases to validate proper privileged vs unprivileged
> loop detection behavior. conditional_loop2 is the one reported by Hao
> Sun that triggered this set of fixes.
>
> Suggested-by: Hao Sun <sunhao.th@gmail.com>
> Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Acked-by: Eduard Zingerman <eddyz87@gmail.com>
prev parent reply other threads:[~2023-11-09 22:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 23:11 [PATCH bpf-next 0/4] BPF control flow graph and precision backtrack fixes Andrii Nakryiko
2023-11-08 23:11 ` [PATCH bpf-next 1/4] bpf: handle ldimm64 properly in check_cfg() Andrii Nakryiko
2023-11-09 22:25 ` Eduard Zingerman
2023-11-08 23:11 ` [PATCH bpf-next 2/4] bpf: fix precision backtracking instruction iteration Andrii Nakryiko
2023-11-09 17:20 ` Eduard Zingerman
2023-11-09 23:18 ` Andrii Nakryiko
2023-11-09 23:28 ` Andrii Nakryiko
2023-11-09 23:37 ` Eduard Zingerman
2023-11-08 23:11 ` [PATCH bpf-next 3/4] bpf: fix control-flow graph checking in privileged mode Andrii Nakryiko
2023-11-09 22:00 ` Eduard Zingerman
2023-11-09 23:25 ` Andrii Nakryiko
2023-11-10 1:26 ` Alexei Starovoitov
2023-11-10 3:41 ` Andrii Nakryiko
2023-11-10 4:08 ` Alexei Starovoitov
2023-11-10 5:31 ` Andrii Nakryiko
2023-11-10 5:33 ` Andrii Nakryiko
2023-11-08 23:11 ` [PATCH bpf-next 4/4] selftests/bpf: add more test cases for check_cfg() Andrii Nakryiko
2023-11-09 22:21 ` Eduard Zingerman [this message]
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=3e8f251498ecaac279b3e60e0f37716c3c5fa34b.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@meta.com \
--cc=martin.lau@kernel.org \
--cc=sunhao.th@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