BPF List
 help / color / mirror / Atom feed
From: Kumar Kartikeya Dwivedi <memxor@gmail.com>
To: bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
	Andrii Nakryiko <andrii@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Martin KaFai Lau <martin.lau@kernel.org>
Subject: [PATCH bpf-next v1 0/2] Follow ups for bpf-list set
Date: Sat, 19 Nov 2022 00:29:36 +0530	[thread overview]
Message-ID: <20221118185938.2139616-1-memxor@gmail.com> (raw)

Make a few changes
 - Remove bpf_global_ma_set check at runtime, disallow calling bpf_obj_new during verification
 - Disable spin lock failure test when JIT does not support kfunc (s390x)

Kumar Kartikeya Dwivedi (2):
  bpf: Disallow calling bpf_obj_new_impl on bpf_mem_alloc_init failure
  selftests/bpf: Skip spin lock failure test on s390x

 kernel/bpf/helpers.c                               |  2 --
 kernel/bpf/verifier.c                              | 13 ++++++++++++-
 tools/testing/selftests/bpf/prog_tests/spin_lock.c |  6 ++++++
 3 files changed, 18 insertions(+), 3 deletions(-)


base-commit: db6bf999544c8c8dcae093e91eba4570647874b1
-- 
2.38.1


             reply	other threads:[~2022-11-18 19:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18 18:59 Kumar Kartikeya Dwivedi [this message]
2022-11-18 18:59 ` [PATCH bpf-next v1 1/2] bpf: Disallow calling bpf_obj_new_impl on bpf_mem_alloc_init failure Kumar Kartikeya Dwivedi
2022-11-18 20:17   ` Alexei Starovoitov
2022-11-20 20:46     ` Kumar Kartikeya Dwivedi
2022-11-20 22:29       ` Alexei Starovoitov
2022-11-18 18:59 ` [PATCH bpf-next v1 2/2] selftests/bpf: Skip spin lock failure test on s390x Kumar Kartikeya Dwivedi
2022-11-18 20:20 ` [PATCH bpf-next v1 0/2] Follow ups for bpf-list set patchwork-bot+netdevbpf

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=20221118185938.2139616-1-memxor@gmail.com \
    --to=memxor@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=martin.lau@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