From: Greg KH <gregkh@linuxfoundation.org>
To: Jean-Philippe Brucker <jean-philippe@linaro.org>
Cc: RAJESH DASARI <raajeshdasari@gmail.com>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org,
df@google.com
Subject: Re: bpf selftest failed in 5.4.210 kernel
Date: Fri, 19 Aug 2022 12:57:09 +0200 [thread overview]
Message-ID: <Yv9shQ3i49efHG6f@kroah.com> (raw)
In-Reply-To: <Yv3wZLuPEL9B/h83@myrica>
On Thu, Aug 18, 2022 at 08:55:16AM +0100, Jean-Philippe Brucker wrote:
> On Thu, Aug 18, 2022 at 07:24:03AM +0200, Greg KH wrote:
> > On Wed, Aug 17, 2022 at 09:22:00PM +0300, RAJESH DASARI wrote:
> > > Hi ,
> > >
> > > We are running bpf selftests on 5.4.210 kernel version and we see that
> > > test case 11 of test_align failed. Please find the below error.
> > >
> > > selftests: bpf: test_align
> > > Test 11: pointer variable subtraction ... Failed to find match 16:
> > > R5_w=pkt(id=2,off=0,r=0,umin_value=2,umax_value=1082,var_off=(0x2;
> > > 0xfffffffc)
> > > # func#0 @0
> > > # 0: R1=ctx(id=0,off=0,imm=0) R10=fp0
> > > # 0: (61) r2 = *(u32 *)(r1 +76)
> > > # 1: R1=ctx(id=0,off=0,imm=0) R2_w=pkt(id=0,off=0,r=0,imm=0) R10=fp0
> > > # 1: (61) r3 = *(u32 *)(r1 +80)
> > >
> > > For complete errors please see the attached file. The same test case
> > > execution was successful in the 5.4.209 version , could you please let
> > > me know any known issue with the recent changes in 5.4.210 and how to
> > > fix these errors.
> >
> > Can you use 'git bisect' to find the offending commit?
>
> It probably is 6098562ed9df ("selftests/bpf: Fix "dubious pointer
> arithmetic" test")
> https://lore.kernel.org/all/20220803145005.2385039-6-ovidiu.panait@windriver.com/
> Could you try reverting that?
>
> The patch didn't have a Fixes: tags, because the bugfix it refers to was
> merged at the same time. That bugfix is upstream commit b02709587ea3
> ("bpf: Fix propagation of 32-bit signed bounds from 64-bit bounds.")
>
> Since b02709587ea3 was only backported down to 5.10, this fix shouldn't be
> in 5.4. Sorry for not catching this earlier.
Can you send in a revert for this?
thanks,
greg k-h
next prev parent reply other threads:[~2022-08-19 10:57 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 [this message]
2022-08-19 16:20 ` RAJESH DASARI
2022-08-20 7:00 ` Greg KH
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=Yv9shQ3i49efHG6f@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