From: Greg KH <gregkh@linuxfoundation.org>
To: Ovidiu Panait <ovidiu.panait@windriver.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 4.19 1/4] selftests/bpf: add selftest part of "bpf: Fix the off-by-two error in range markings"
Date: Mon, 15 Aug 2022 14:15:11 +0200 [thread overview]
Message-ID: <Yvo4zy8quy9lYall@kroah.com> (raw)
In-Reply-To: <029942ab-365d-0e69-7b5a-3b568518fd02@windriver.com>
On Sun, Aug 14, 2022 at 06:08:26PM +0300, Ovidiu Panait wrote:
>
> On 8/14/22 17:44, Greg KH wrote:
> > [Please note: This e-mail is from an EXTERNAL e-mail address]
> >
> > On Sun, Aug 14, 2022 at 04:58:56PM +0300, Ovidiu Panait wrote:
> > > Hi Greg,
> > >
> > > On 8/13/22 16:10, Greg KH wrote:
> > > > [Please note: This e-mail is from an EXTERNAL e-mail address]
> > > >
> > > > 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.
> > > This patch includes the selftest part of upstream commit:
> > >
> > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=2fa7d94afc1a
> > >
> > >
> > > The 4.19 backport of the above commit did not include the selftest updates:
> > >
> > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c315bd962528
> > I still do not understand, what commit is this coming from that matches
> > it up with what is in Linus's tree?
> The changes come from commit 2fa7d94afc1a ("bpf: Fix the off-by-two error in
> range markings") in Linus's tree.
Then can you please reword the text here to make it obvious what is
happening and resubmit?
thanks,
gre gk-h
next prev parent reply other threads:[~2022-08-15 12:15 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
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 [this message]
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=Yvo4zy8quy9lYall@kroah.com \
--to=gregkh@linuxfoundation.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 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.