[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y6NOZEaDpod+9r/0@kroah.com>
Date: Wed, 21 Dec 2022 19:20:20 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Jiri Slaby <jirislaby@...nel.org>
Cc: Guenter Roeck <linux@...ck-us.net>, stable@...r.kernel.org,
patches@...ts.linux.dev, linux-kernel@...r.kernel.org,
torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
shuah@...nel.org, patches@...nelci.org,
lkft-triage@...ts.linaro.org, pavel@...x.de, jonathanh@...dia.com,
f.fainelli@...il.com, sudipm.mukherjee@...il.com,
srw@...dewatkins.net, rwarsow@....de
Subject: Re: [PATCH 6.1 00/25] 6.1.1-rc1 review
On Wed, Dec 21, 2022 at 07:34:04AM +0100, Jiri Slaby wrote:
> On 20. 12. 22, 17:11, Guenter Roeck wrote:
> > You probably didn't see any reports on mainline because I didn't report
> > the issue there yet. There are so many failures in mainline that it is
> > a bit difficult to keep up.
>
> Just heads up, these are breakages in 6.1 known to me:
>
> an io_uring 32bit test crashes the kernel:
> https://lore.kernel.org/all/c80c1e3f-800b-dc49-f2f5-acc8ceb34d51@gmail.com/
>
> Fixed in io_uring tree.
>
>
> bind() of previously bound port no longer fails:
> https://lore.kernel.org/all/6b971a4e-c7d8-411e-1f92-fda29b5b2fb9@kernel.org/
>
> No fix available and revert close to impossible.
>
>
>
> And most important, mremap() is broken in 6.1, so mostly everything fails in
> some random way:
> https://lore.kernel.org/all/20221216163227.24648-1-vbabka@suse.cz/T/#u
>
> Fixed in -mm.
>
> maybe it can help...
Thanks for the list, I'll keep an eye out for these...
greg k-h
Powered by blists - more mailing lists