[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2024102206-puzzling-demeaning-e190@gregkh>
Date: Tue, 22 Oct 2024 10:57:38 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Florian Fainelli <f.fainelli@...il.com>
Cc: 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, sudipm.mukherjee@...il.com,
srw@...dewatkins.net, rwarsow@....de, conor@...nel.org,
allen.lkml@...il.com, broonie@...nel.org
Subject: Re: [PATCH 6.1 00/91] 6.1.114-rc1 review
On Mon, Oct 21, 2024 at 11:24:26AM -0700, Florian Fainelli wrote:
> On 10/21/24 03:24, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.1.114 release.
> > There are 91 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, 23 Oct 2024 10:22:25 +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/v6.x/stable-review/patch-6.1.114-rc1.gz
> > or in the git tree and branch at:
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.1.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
>
> On ARCH_BRCMSTB using 32-bit and 64-bit ARM kernels, build tested on
> BMIPS_GENERIC:
>
> Tested-by: Florian Fainelli <florian.fainelli@...adcom.com>
>
> There is a new warning that got picked up on ARM 32-buit:
>
> fs/udf/namei.c:878:1: warning: the frame size of 1152 bytes is larger than
> 1024 bytes [-Wframe-larger-than=]
>
> I was not able to locate a fix upstream for this, but it does appear to come
> from ("udf: Convert udf_rename() to new directory iteration code").
Ah, thanks for tracking this down. Odd that it's only showing up here
as these changes are all upstream, perhaps the stack size got increased
in a newer kernel to work around this issue?
thanks,
greg k-h
Powered by blists - more mailing lists