From: Greg KH <gregkh@linuxfoundation.org>
To: Ovidiu Panait <ovidiu.panait@windriver.com>
Cc: stable@vger.kernel.org, bpf@vger.kernel.org, daniel@iogearbox.net
Subject: Re: [PATCH 5.4 0/4] bpf: backport fixes for CVE-2021-34556/CVE-2021-35477
Date: Mon, 13 Sep 2021 11:17:59 +0200 [thread overview]
Message-ID: <YT8XR5AiS5eu3P6D@kroah.com> (raw)
In-Reply-To: <20210907131701.1910024-1-ovidiu.panait@windriver.com>
On Tue, Sep 07, 2021 at 04:16:57PM +0300, Ovidiu Panait wrote:
> With this patchseries all bpf verifier selftests pass (tested in qemu for x86_64):
> root@intel-x86-64:~# ./test_verifier
> ...
> #1057/p XDP pkt read, pkt_meta' <= pkt_data, bad access 1 OK
> #1058/p XDP pkt read, pkt_meta' <= pkt_data, bad access 2 OK
> #1059/p XDP pkt read, pkt_data <= pkt_meta', good access OK
> #1060/p XDP pkt read, pkt_data <= pkt_meta', bad access 1 OK
> #1061/p XDP pkt read, pkt_data <= pkt_meta', bad access 2 OK
> Summary: 1571 PASSED, 0 SKIPPED, 0 FAILED
>
> Daniel Borkmann (3):
> bpf: Introduce BPF nospec instruction for mitigating Spectre v4
> bpf: Fix leakage due to insufficient speculative store bypass
> mitigation
> bpf: Fix pointer arithmetic mask tightening under state pruning
>
> Lorenz Bauer (1):
> bpf: verifier: Allocate idmap scratch in verifier env
Thanks for these, now queued up.
greg k-h
prev parent reply other threads:[~2021-09-13 9:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 13:16 [PATCH 5.4 0/4] bpf: backport fixes for CVE-2021-34556/CVE-2021-35477 Ovidiu Panait
2021-09-07 13:16 ` [PATCH 5.4 1/4] bpf: Introduce BPF nospec instruction for mitigating Spectre v4 Ovidiu Panait
2021-09-07 13:16 ` [PATCH 5.4 2/4] bpf: Fix leakage due to insufficient speculative store bypass mitigation Ovidiu Panait
2021-09-07 13:17 ` [PATCH 5.4 3/4] bpf: verifier: Allocate idmap scratch in verifier env Ovidiu Panait
2021-09-07 13:17 ` [PATCH 5.4 4/4] bpf: Fix pointer arithmetic mask tightening under state pruning Ovidiu Panait
2021-09-13 9:17 ` Greg KH [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=YT8XR5AiS5eu3P6D@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=ovidiu.panait@windriver.com \
--cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).