From: Greg KH <greg@kroah.com>
To: Ovidiu Panait <ovidiu.panait@windriver.com>
Cc: stable@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH 4.19 0/4] bpf: backport fixes for CVE-2021-33624
Date: Fri, 13 Aug 2021 10:38:55 +0200 [thread overview]
Message-ID: <YRYvn51P2Or6deXs@kroah.com> (raw)
In-Reply-To: <20210812170037.2370387-1-ovidiu.panait@windriver.com>
On Thu, Aug 12, 2021 at 08:00:33PM +0300, Ovidiu Panait wrote:
> NOTE: the fixes were manually adjusted to apply to 4.19, so copying bpf@ to see
> if there are any concerns.
>
> With this patchseries all bpf verifier selftests pass:
> root@intel-x86-64:~# ./test_verifier
> ...
> #657/u pass modified ctx pointer to helper, 2 OK
> #657/p pass modified ctx pointer to helper, 2 OK
> #658/p pass modified ctx pointer to helper, 3 OK
> #659/p mov64 src == dst OK
> #660/p mov64 src != dst OK
> #661/u calls: ctx read at start of subprog OK
> #661/p calls: ctx read at start of subprog OK
> Summary: 925 PASSED, 0 SKIPPED, 0 FAILED
>
> Daniel Borkmann (4):
> bpf: Inherit expanded/patched seen count from old aux data
> bpf: Do not mark insn as seen under speculative path verification
> bpf: Fix leakage under speculation on mispredicted branches
> bpf, selftests: Adjust few selftest outcomes wrt unreachable code
All now queued up, thanks!
greg k-h
prev parent reply other threads:[~2021-08-13 8:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 17:00 [PATCH 4.19 0/4] bpf: backport fixes for CVE-2021-33624 Ovidiu Panait
2021-08-12 17:00 ` [PATCH 4.19 1/4] bpf: Inherit expanded/patched seen count from old aux data Ovidiu Panait
2021-08-12 17:00 ` [PATCH 4.19 2/4] bpf: Do not mark insn as seen under speculative path verification Ovidiu Panait
2021-08-12 17:00 ` [PATCH 4.19 3/4] bpf: Fix leakage under speculation on mispredicted branches Ovidiu Panait
2021-08-12 17:00 ` [PATCH 4.19 4/4] bpf, selftests: Adjust few selftest outcomes wrt unreachable code Ovidiu Panait
2021-08-13 8:38 ` 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=YRYvn51P2Or6deXs@kroah.com \
--to=greg@kroah.com \
--cc=bpf@vger.kernel.org \
--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