From: Greg KH <gregkh@linuxfoundation.org>
To: RAJESH DASARI <raajeshdasari@gmail.com>
Cc: Jean-Philippe Brucker <jean-philippe@linaro.org>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org,
df@google.com
Subject: Re: bpf selftest failed in 5.4.210 kernel
Date: Sat, 20 Aug 2022 09:00:49 +0200 [thread overview]
Message-ID: <YwCGoRt6ifOC6mCD@kroah.com> (raw)
In-Reply-To: <CAPXMrf8VsNMKNLxFjdytk57mk_9ZC0avg1qCGLSMOZNirpdboQ@mail.gmail.com>
On Fri, Aug 19, 2022 at 07:20:11PM +0300, RAJESH DASARI wrote:
> Hi ,
>
> I did some more tests , Please find the observation below.
>
> step 1: On v5.4.210 kernel , I reverted only commit bpf: Verifer,
> adjust_scalar_min_max_vals to always call update_reg_bounds()
> 7c1134c7da997523e2834dd516e2ddc51920699a , compiled the kernel and
> booted the system with the new kernel.
> step 2: On system with newly compiled kernel , I clone the v54.4.210
> source code and reverted commit selftests/bpf: Fix test_align
> verifier log patterns and selftests/bpf: Fix "dubious pointer
> arithmetic" test , then ran the selftests, test_align test cases
> execution was successful.
> step 3: If i revert only selftests/bpf: Fix "dubious pointer
> arithmetic" test , test cases are still failing.
>
>
>
> Please find the attached PDF for the other scenarios which I have executed.
For obvious reasons, we can't read random .pdf files sent to us. Please
put it all in text.
thanks,
greg k-h
next prev parent reply other threads:[~2022-08-20 7:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 18:22 bpf selftest failed in 5.4.210 kernel RAJESH DASARI
2022-08-18 5:24 ` Greg KH
2022-08-18 7:55 ` Jean-Philippe Brucker
2022-08-19 10:57 ` Greg KH
2022-08-19 16:20 ` RAJESH DASARI
2022-08-20 7:00 ` Greg KH [this message]
2022-08-22 19:23 ` RAJESH DASARI
2022-08-23 7:04 ` Greg KH
2022-08-23 7:31 ` RAJESH DASARI
2022-08-23 18:34 ` Jean-Philippe Brucker
2022-08-23 20:03 ` Ovidiu Panait
2022-08-23 20:25 ` Ovidiu Panait
2022-08-24 13:55 ` Jean-Philippe Brucker
2022-08-18 18:33 ` RAJESH DASARI
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=YwCGoRt6ifOC6mCD@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=df@google.com \
--cc=jean-philippe@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raajeshdasari@gmail.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