From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
To: <bpf@vger.kernel.org>, <linuxppc-dev@lists.ozlabs.org>
Cc: Jiri Olsa <jolsa@redhat.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Brendan Jackman <jackmanb@google.com>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Daniel Borkmann <daniel@iogearbox.net>
Subject: [PATCH 0/2] powerpc/bpf: Fix issue with atomic ops
Date: Thu, 1 Jul 2021 20:38:57 +0530 [thread overview]
Message-ID: <cover.1625145429.git.naveen.n.rao@linux.vnet.ibm.com> (raw)
The first patch fixes an issue that causes a soft lockup on ppc64 with
the BPF_ATOMIC bounds propagation verifier test. The second one updates
ppc32 JIT to reject atomic operations properly.
- Naveen
Naveen N. Rao (2):
powerpc/bpf: Fix detecting BPF atomic instructions
powerpc/bpf: Reject atomic ops in ppc32 JIT
arch/powerpc/net/bpf_jit_comp32.c | 14 +++++++++++---
arch/powerpc/net/bpf_jit_comp64.c | 4 ++--
2 files changed, 13 insertions(+), 5 deletions(-)
base-commit: 086d9878e1092e7e69a69676ee9ec792690abb1d
--
2.31.1
WARNING: multiple messages have this Message-ID (diff)
From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
To: <bpf@vger.kernel.org>, <linuxppc-dev@lists.ozlabs.org>
Cc: Brendan Jackman <jackmanb@google.com>,
Jiri Olsa <jolsa@redhat.com>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Daniel Borkmann <daniel@iogearbox.net>
Subject: [PATCH 0/2] powerpc/bpf: Fix issue with atomic ops
Date: Thu, 1 Jul 2021 20:38:57 +0530 [thread overview]
Message-ID: <cover.1625145429.git.naveen.n.rao@linux.vnet.ibm.com> (raw)
The first patch fixes an issue that causes a soft lockup on ppc64 with
the BPF_ATOMIC bounds propagation verifier test. The second one updates
ppc32 JIT to reject atomic operations properly.
- Naveen
Naveen N. Rao (2):
powerpc/bpf: Fix detecting BPF atomic instructions
powerpc/bpf: Reject atomic ops in ppc32 JIT
arch/powerpc/net/bpf_jit_comp32.c | 14 +++++++++++---
arch/powerpc/net/bpf_jit_comp64.c | 4 ++--
2 files changed, 13 insertions(+), 5 deletions(-)
base-commit: 086d9878e1092e7e69a69676ee9ec792690abb1d
--
2.31.1
next reply other threads:[~2021-07-01 15:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 15:08 Naveen N. Rao [this message]
2021-07-01 15:08 ` [PATCH 0/2] powerpc/bpf: Fix issue with atomic ops Naveen N. Rao
2021-07-01 15:08 ` [PATCH 1/2] powerpc/bpf: Fix detecting BPF atomic instructions Naveen N. Rao
2021-07-01 15:08 ` Naveen N. Rao
2021-07-01 16:03 ` Alexei Starovoitov
2021-07-01 16:03 ` Alexei Starovoitov
2021-07-01 19:32 ` Naveen N. Rao
2021-07-01 19:32 ` Naveen N. Rao
2021-07-01 19:33 ` Alexei Starovoitov
2021-07-01 19:33 ` Alexei Starovoitov
2021-07-02 10:26 ` Jiri Olsa
2021-07-02 10:26 ` Jiri Olsa
2021-07-01 15:08 ` [PATCH 2/2] powerpc/bpf: Reject atomic ops in ppc32 JIT Naveen N. Rao
2021-07-01 15:08 ` Naveen N. Rao
2021-07-01 16:36 ` Christophe Leroy
2021-07-01 19:36 ` Naveen N. Rao
2021-07-01 19:36 ` Naveen N. Rao
2021-07-06 10:52 ` [PATCH 0/2] powerpc/bpf: Fix issue with atomic ops Michael Ellerman
2021-07-06 10:52 ` Michael Ellerman
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=cover.1625145429.git.naveen.n.rao@linux.vnet.ibm.com \
--to=naveen.n.rao@linux.vnet.ibm.com \
--cc=alexei.starovoitov@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jackmanb@google.com \
--cc=jolsa@redhat.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.