From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
open list <linux-kernel@vger.kernel.org>,
Shuah Khan <shuah@kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
patches@kernelci.org, lkft-triage@lists.linaro.org,
Jon Hunter <jonathanh@nvidia.com>,
linux-stable <stable@vger.kernel.org>,
pavel@denx.de, Andrew Morton <akpm@linux-foundation.org>,
Guenter Roeck <linux@roeck-us.net>, LTP List <ltp@lists.linux.it>
Subject: Re: [PATCH 5.11 000/773] 5.11.3-rc3 review
Date: Thu, 4 Mar 2021 12:23:15 +0100 [thread overview]
Message-ID: <YEDDIzz32JqSvi1S@kroah.com> (raw)
In-Reply-To: <CA+G9fYvkW+84U9e0Cjft_pq9bGnBBqCXST7Hg+gx4pKNyuGPFQ@mail.gmail.com>
On Wed, Mar 03, 2021 at 02:02:20PM +0530, Naresh Kamboju wrote:
> On Wed, 3 Mar 2021 at 00:59, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > This is the start of the stable review cycle for the 5.11.3 release.
> > There are 773 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, 04 Mar 2021 19:25:07 +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.11.3-rc3.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.11.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
>
>
> Results from Linaro’s test farm.
> All our builds are getting PASS now.
> But,
> Regressions detected on all devices (arm64, arm, x86_64 and i386).
> LTP pty test case hangup01 failed on all devices
>
> hangup01 1 TFAIL : hangup01.c:133: unexpected message 3
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> This failure is specific to stable-rc v5.10.20-rc4 and v5.11.3-rc3
> Test PASS on the v5.12-rc1 mainline and Linux next kernel.
>
> Following two commits caused this test failure,
>
> Linus Torvalds <torvalds@linux-foundation.org>
> tty: implement read_iter
>
> Linus Torvalds <torvalds@linux-foundation.org>
> tty: convert tty_ldisc_ops 'read()' function to take a kernel pointer
>
> Test case failed link,
> https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-5.11.y/build/v5.11.2-774-g6ca52dbc58df/testrun/4070143/suite/ltp-pty-tests/test/hangup01/log
>
Thanks for testing them all, I'll try to debug this later today...
greg k-h
next prev parent reply other threads:[~2021-03-04 11:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 19:29 [PATCH 5.11 000/773] 5.11.3-rc3 review Greg Kroah-Hartman
2021-03-03 8:32 ` Naresh Kamboju
2021-03-04 11:23 ` Greg Kroah-Hartman [this message]
2021-03-04 16:52 ` Guenter Roeck
2021-03-04 17:02 ` Greg Kroah-Hartman
2021-03-04 17:58 ` Naresh Kamboju
2021-03-03 9:28 ` Jon Hunter
2021-03-03 20:08 ` Guenter Roeck
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=YEDDIzz32JqSvi1S@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=f.fainelli@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=ltp@lists.linux.it \
--cc=naresh.kamboju@linaro.org \
--cc=patches@kernelci.org \
--cc=pavel@denx.de \
--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