From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: open list <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Guenter Roeck <linux@roeck-us.net>, Shuah Khan <shuah@kernel.org>,
patches@kernelci.org,
Ben Hutchings <ben.hutchings@codethink.co.uk>,
lkft-triage@lists.linaro.org,
linux- stable <stable@vger.kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
john.fastabend@gmail.com, komachi.yoshiki@gmail.com,
Andrii Nakryiko <andriin@fb.com>,
lukenels@cs.washington.edu, Netdev <netdev@vger.kernel.org>,
bpf <bpf@vger.kernel.org>
Subject: Re: [PATCH 5.5 000/171] 5.5.14-rc2 review
Date: Wed, 1 Apr 2020 08:11:31 +0200 [thread overview]
Message-ID: <20200401061131.GA1907105@kroah.com> (raw)
In-Reply-To: <CA+G9fYuU-5o5DG1VSQuCPx=TSs61-1jBekdGb5yvMRz4ur3BQg@mail.gmail.com>
On Wed, Apr 01, 2020 at 04:18:41AM +0530, Naresh Kamboju wrote:
> On Tue, 31 Mar 2020 at 21:02, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > This is the start of the stable review cycle for the 5.5.14 release.
> > There are 171 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with these being applied, please
> > let me know.
> >
> > Responses should be made by Thu, 02 Apr 2020 14:12:02 +0000.
> > Anything received after that time might be too late.
> >
> > The whole patch series can be found in one patch at:
> > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.5.14-rc2.gz
> > or in the git tree and branch at:
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.5.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
>
>
> Results from Linaro’s test farm.
> Regressions on x86_64 and i386.
>
> selftests bpf test_verifier reports as failed.
> This test PASSED on v5.5.13
>
> #554/p jgt32: range bound deduction, reg op imm FAIL
> Failed to load prog 'Success'!
> R8 unbounded memory access, make sure to bounds check any array access
> into a map
> verification time 141 usec
> stack depth 8
> processed 16 insns (limit 1000000) max_states_per_insn 0 total_states
> 1 peak_states 1 mark_read 1
> #555/p jgt32: range bound deduction, reg1 op reg2, reg1 unknown FAIL
> Failed to load prog 'Success'!
> R8 unbounded memory access, make sure to bounds check any array access
> into a map
> verification time 94 usec
> stack depth 8
> processed 17 insns (limit 1000000) max_states_per_insn 0 total_states
> 1 peak_states 1 mark_read 1
> #556/p jle32: range bound deduction, reg1 op reg2, reg2 unknown FAIL
> Failed to load prog 'Success'!
> R8 unbounded memory access, make sure to bounds check any array access
> into a map
> verification time 68 usec
> stack depth 8
> processed 17 insns (limit 1000000) max_states_per_insn 0 total_states
> 1 peak_states 1 mark_read 1
Can you run 'git bisect' to find the offending patch?
thanks,
greg k-h
next prev parent reply other threads:[~2020-04-01 6:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 15:32 [PATCH 5.5 000/171] 5.5.14-rc2 review Greg Kroah-Hartman
2020-03-31 22:28 ` shuah
2020-03-31 22:48 ` Naresh Kamboju
2020-04-01 6:11 ` Greg Kroah-Hartman [this message]
2020-04-01 8:03 ` Daniel Borkmann
2020-04-01 8:56 ` Greg Kroah-Hartman
2020-04-01 0:43 ` Vitor Massaru Iha
2020-04-01 2:25 ` Guenter Roeck
2020-04-01 8:57 ` Jon Hunter
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=20200401061131.GA1907105@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=andriin@fb.com \
--cc=ben.hutchings@codethink.co.uk \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=komachi.yoshiki@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=lukenels@cs.washington.edu \
--cc=naresh.kamboju@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=patches@kernelci.org \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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).