Re: [PATCH 5.10 000/657] 5.10.20-rc4 review

From: Naresh Kamboju
Date: Thu Mar 04 2021 - 12:58:04 EST


On Thu, 4 Mar 2021 at 01:34, Guenter Roeck <linux@xxxxxxxxxxxx> wrote:
>
> On 3/3/21 8:12 AM, Naresh Kamboju wrote:
> > On Wed, 3 Mar 2021 at 00:59, Greg Kroah-Hartman
> > <gregkh@xxxxxxxxxxxxxxxxxxx> wrote:
> >>
> >> This is the start of the stable review cycle for the 5.10.20 release.
> >> There are 657 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.10.20-rc4.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.10.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@xxxxxxxxxx>
> >
> > 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@xxxxxxxxxxxxxxxxxxxx>
> > tty: implement read_iter
> >
> > Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
> > tty: convert tty_ldisc_ops 'read()' function to take a kernel pointer
> >
>
> Upstream has:
>
> e71a8d5cf4b4 tty: fix up iterate_tty_read() EOVERFLOW handling
> ddc5fda74561 tty: fix up hung_up_tty_read() conversion
>
> Those are not present in v5.10.20-rc4, which may possibly
> explain the problem.

I have applied these two patches and the reported problem did not solve.

- Naresh