From: Eduard Zingerman <eddyz87@gmail.com>
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: bpf@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Martin KaFai Lau <martin.lau@kernel.org>,
Tao Lyu <tao.lyu@epfl.ch>,
Mathias Payer <mathias.payer@nebelwelt.net>,
Meng Xu <meng.xu.cs@uwaterloo.ca>,
Sanidhya Kashyap <sanidhya.kashyap@epfl.ch>
Subject: Re: [PATCH bpf-next v2 3/4] selftests/bpf: Add test for reading from STACK_INVALID slots
Date: Wed, 27 Nov 2024 18:01:14 -0800 [thread overview]
Message-ID: <07cb2eacc4f56f9b60f9c41e9f398bb20618f3f1.camel@gmail.com> (raw)
In-Reply-To: <CAP01T76567Rf4iou=9CF+iWOVQp0VHwvEcUyaeS_2kx9hZBgWQ@mail.gmail.com>
On Thu, 2024-11-28 at 02:57 +0100, Kumar Kartikeya Dwivedi wrote:
> On Thu, 28 Nov 2024 at 02:50, Eduard Zingerman <eddyz87@gmail.com> wrote:
> >
> > On Wed, 2024-11-27 at 13:20 -0800, Kumar Kartikeya Dwivedi wrote:
> > > Ensure that when CAP_PERFMON is dropped, and the verifier sees
> > > allow_ptr_leaks as false, we are not permitted to read from a
> > > STACK_INVALID slot. Without the fix, the test will report unexpected
> > > success in loading.
> > >
> > > Since we need to control the capabilities when loading this test to only
> > > retain CAP_BPF, refactor support added to do the same for
> > > test_verifier_mtu and reuse it for this selftest to avoid copy-paste.
> > >
> > > Signed-off-by: Kumar Kartikeya Dwivedi <memxor@gmail.com>
> > > ---
> > > .../selftests/bpf/prog_tests/verifier.c | 41 ++++++++++++++++---
> > > .../bpf/progs/verifier_stack_noperfmon.c | 21 ++++++++++
> > > 2 files changed, 56 insertions(+), 6 deletions(-)
> > > create mode 100644 tools/testing/selftests/bpf/progs/verifier_stack_noperfmon.c
> > >
> > > diff --git a/tools/testing/selftests/bpf/prog_tests/verifier.c b/tools/testing/selftests/bpf/prog_tests/verifier.c
> > > index d9f65adb456b..aaf4324e8ef0 100644
> > > --- a/tools/testing/selftests/bpf/prog_tests/verifier.c
> > > +++ b/tools/testing/selftests/bpf/prog_tests/verifier.c
> > > @@ -63,6 +63,7 @@
> > > #include "verifier_prevent_map_lookup.skel.h"
> > > #include "verifier_private_stack.skel.h"
> > > #include "verifier_raw_stack.skel.h"
> > > +#include "verifier_stack_noperfmon.skel.h"
> > > #include "verifier_raw_tp_writable.skel.h"
> > > #include "verifier_reg_equal.skel.h"
> > > #include "verifier_ref_tracking.skel.h"
> > > @@ -226,22 +227,50 @@ void test_verifier_xdp_direct_packet_access(void) { RUN(verifier_xdp_direct_pack
> > > void test_verifier_bits_iter(void) { RUN(verifier_bits_iter); }
> > > void test_verifier_lsm(void) { RUN(verifier_lsm); }
> > >
> > > -void test_verifier_mtu(void)
> > > +static int test_verifier_disable_caps(__u64 *caps)
> >
> > The original thread [0] discusses __caps_unpriv macro.
> > I'd prefer such macro over these changes to prog_tests/verifier.c,
> > were there any technical problems with code suggested in [0]?
> >
> > [0] https://lore.kernel.org/bpf/a1e48f5d9ae133e19adc6adf27e19d585e06bab4.camel@gmail.com/#t
> >
>
> I think that patch worked as well, but I got to look at this now after
> all these months, and concluded that
> what Daniel did in
> https://lore.kernel.org/bpf/20241021152809.33343-5-daniel@iogearbox.net
> was also
> acceptable and preferred.
>
> I can add your patch to this set and respin, or post a follow-up converting
> test_verifier_mtu to it as well. Whatever is preferred.
Patch #1 would need a respin because the comment for mark_stack_slot_misc() needs fixing.
If you agree with adding __caps_unpriv, could you please make it a part of v3?
[...]
next prev parent reply other threads:[~2024-11-28 2:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 21:20 [PATCH bpf-next v2 0/4] Fixes for stack with allow_ptr_leaks Kumar Kartikeya Dwivedi
2024-11-27 21:20 ` [PATCH bpf-next v2 1/4] bpf: Don't relax STACK_INVALID to STACK_MISC when not allow_ptr_leaks Kumar Kartikeya Dwivedi
2024-11-28 1:09 ` Eduard Zingerman
2024-11-27 21:20 ` [PATCH bpf-next v2 2/4] bpf: Fix narrow scalar spill onto 64-bit spilled scalar slots Kumar Kartikeya Dwivedi
2024-11-28 1:21 ` Eduard Zingerman
2024-11-27 21:20 ` [PATCH bpf-next v2 3/4] selftests/bpf: Add test for reading from STACK_INVALID slots Kumar Kartikeya Dwivedi
2024-11-28 1:50 ` Eduard Zingerman
2024-11-28 1:57 ` Kumar Kartikeya Dwivedi
2024-11-28 2:01 ` Eduard Zingerman [this message]
2024-11-28 2:07 ` Kumar Kartikeya Dwivedi
2024-11-27 21:20 ` [PATCH bpf-next v2 4/4] selftests/bpf: Add test for narrow spill into 64-bit spilled scalar Kumar Kartikeya Dwivedi
2024-11-28 1:56 ` Eduard Zingerman
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=07cb2eacc4f56f9b60f9c41e9f398bb20618f3f1.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=martin.lau@kernel.org \
--cc=mathias.payer@nebelwelt.net \
--cc=memxor@gmail.com \
--cc=meng.xu.cs@uwaterloo.ca \
--cc=sanidhya.kashyap@epfl.ch \
--cc=tao.lyu@epfl.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