linux-kernel - Re: [PATCH 6.0 00/74] 6.0.17-rc1 review

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Y7VeN+WpVKqivRGL@kroah.com>
Date:   Wed, 4 Jan 2023 12:08:39 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Sudip Mukherjee <sudipm.mukherjee@...il.com>
Cc:     "David S. Miller" <davem@...emloft.net>, stable@...r.kernel.org,
        patches@...ts.linux.dev, linux-kernel@...r.kernel.org,
        torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
        linux@...ck-us.net, shuah@...nel.org, patches@...nelci.org,
        lkft-triage@...ts.linaro.org, pavel@...x.de, jonathanh@...dia.com,
        f.fainelli@...il.com, srw@...dewatkins.net, rwarsow@....de
Subject: Re: [PATCH 6.0 00/74] 6.0.17-rc1 review

On Tue, Jan 03, 2023 at 10:59:58PM +0000, Sudip Mukherjee wrote:
> On Tue, 3 Jan 2023 at 10:37, Sudip Mukherjee (Codethink)
> <sudipm.mukherjee@...il.com> wrote:
> >
> > Hi Greg,
> >
> > On Mon, Jan 02, 2023 at 12:21:33PM +0100, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 6.0.17 release.
> > > There are 74 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 Wed, 04 Jan 2023 11:05:34 +0000.
> > > Anything received after that time might be too late.
> >
> 
> <snip>
> 
> >
> > mips: Booted on ci20 board. VNC server did not start, will try a bisect
> > later tonight.
> 
> bisect pointed to 2575eebf1bd2 ("net: Return errno in
> sk->sk_prot->get_port().") introduced in v6.0.16
> Reverting it on top of v6.0.16 and 6.0.17-rc1 fixed the problem.
> 
> This is also in v6.1.y but the issue is not seen there, and I am
> trying to figure out why.

As there's probably only going to be one more 6.0.y release before it is
end-of-life, if you can't figure it out, not that big of a deal :)

thanks,

greg k-h