From: Greg KH <gregkh@linuxfoundation.org>
To: Ovidiu Panait <ovidiu.panait@windriver.com>
Cc: stable@vger.kernel.org, Maxim Mikityanskiy <maximmi@nvidia.com>
Subject: Re: [PATCH 4.19 1/4] selftests/bpf: add selftest part of "bpf: Fix the off-by-two error in range markings"
Date: Sat, 13 Aug 2022 15:10:53 +0200 [thread overview]
Message-ID: <Yvei3RLnHqGgb9yp@kroah.com> (raw)
In-Reply-To: <20220809073947.33804-2-ovidiu.panait@windriver.com>
On Tue, Aug 09, 2022 at 10:39:44AM +0300, Ovidiu Panait wrote:
> From: Maxim Mikityanskiy <maximmi@nvidia.com>
>
> The 4.19 backport of upstream commit 2fa7d94afc1a ("bpf: Fix the off-by-two
> error in range markings") did not include the selftest changes, so currently
> there are 8 verifier selftests that are failing:
> # root@intel-x86-64:~# ./test_verifier
> ...
> #495/p XDP pkt read, pkt_end > pkt_data', bad access 1 FAIL
> #498/p XDP pkt read, pkt_data' < pkt_end, bad access 1 FAIL
> #504/p XDP pkt read, pkt_data' >= pkt_end, bad access 1 FAIL
> #513/p XDP pkt read, pkt_end <= pkt_data', bad access 1 FAIL
> #519/p XDP pkt read, pkt_data > pkt_meta', bad access 1 FAIL
> #522/p XDP pkt read, pkt_meta' < pkt_data, bad access 1 FAIL
> #528/p XDP pkt read, pkt_meta' >= pkt_data, bad access 1 FAIL
> #537/p XDP pkt read, pkt_data <= pkt_meta', bad access 1 FAIL
> Summary: 924 PASSED, 0 SKIPPED, 8 FAILED
>
> Cherry-pick the selftest changes to fix these.
What specific "selftest changes" are you cherry-picking here? I can't
take this commit without that reference.
thanks,
greg k-h
next prev parent reply other threads:[~2022-08-13 13:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 7:39 [PATCH 4.19 0/4] bpf: fix CVE-2021-4159 Ovidiu Panait
2022-08-09 7:39 ` [PATCH 4.19 1/4] selftests/bpf: add selftest part of "bpf: Fix the off-by-two error in range markings" Ovidiu Panait
2022-08-13 13:10 ` Greg KH [this message]
2022-08-14 13:58 ` Ovidiu Panait
2022-08-14 14:44 ` Greg KH
2022-08-14 15:08 ` Ovidiu Panait
2022-08-15 12:15 ` Greg KH
2022-08-09 7:39 ` [PATCH 4.19 2/4] bpf: Verifer, adjust_scalar_min_max_vals to always call update_reg_bounds() Ovidiu Panait
2022-08-09 7:39 ` [PATCH 4.19 3/4] selftests/bpf: Fix test_align verifier log patterns Ovidiu Panait
2022-08-09 7:39 ` [PATCH 4.19 4/4] selftests/bpf: Fix "dubious pointer arithmetic" test Ovidiu Panait
2022-08-13 13:12 ` [PATCH 4.19 0/4] bpf: fix CVE-2021-4159 Greg KH
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=Yvei3RLnHqGgb9yp@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=maximmi@nvidia.com \
--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).