[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2025100105-strewn-waving-35de@gregkh>
Date: Wed, 1 Oct 2025 12:50:13 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@...aro.org>
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, f.fainelli@...il.com,
sudipm.mukherjee@...il.com, rwarsow@....de, conor@...nel.org,
hargar@...rosoft.com, broonie@...nel.org, achill@...ill.org,
Dan Carpenter <dan.carpenter@...aro.org>,
Arnd Bergmann <arnd@...db.de>, linux-fsdevel@...r.kernel.org,
linux-block <linux-block@...r.kernel.org>,
Anders Roxell <anders.roxell@...aro.org>,
Ben Copeland <benjamin.copeland@...aro.org>
Subject: Re: [PATCH 5.10 000/122] 5.10.245-rc1 review
On Wed, Oct 01, 2025 at 12:57:27AM +0530, Naresh Kamboju wrote:
> On Tue, 30 Sept 2025 at 20:24, Greg Kroah-Hartman
> <gregkh@...uxfoundation.org> wrote:
> >
> > This is the start of the stable review cycle for the 5.10.245 release.
> > There are 122 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, 02 Oct 2025 14:37:59 +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.245-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-5.10.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
>
> The following LTP syscalls failed on stable-rc 5.10.
> Noticed on both 5.10.243-rc1 and 5.10.245-rc1
>
> First seen on 5.10.243-rc1.
>
> ltp-syscalls
> - fanotify13
> - fanotify14
> - fanotify15
> - fanotify16
> - fanotify21
> - landlock04
> - ioctl_ficlone02
>
> Test regression: LTP syscalls fanotify13/14/15/16/21 TBROK: mkfs.vfat
> failed with exit code 1
>
> Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>
>
> We are investigating and running bisections.
>
> ### Test log
> tst_test.c:1888: TINFO: === Testing on vfat ===
> tst_test.c:1217: TINFO: Formatting /dev/loop0 with vfat opts='' extra opts=''
> mkfs.vfat: Partitions or virtual mappings on device '/dev/loop0', not
> making filesystem (use -I to override)
> tst_test.c:1217: TBROK: mkfs.vfat failed with exit code 1
> HINT: You _MAY_ be missing kernel fixes:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c285a2f01d69
You are not missing this "fix".
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bc2473c90fca
You are missing that one, but why is a overlayfs commit being cared
about for vfat?
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c45beebfde34a
Another overlayfs patch that is not backported that far. Again, why is
this a hint for vfat?
thanks,
greg k-h
Powered by blists - more mailing lists