[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1081af30-1273-4a9a-a864-f59f1cb54fd1@t-8ch.de>
Date: Wed, 18 Jun 2025 16:15:09 +0200
From: Thomas Weißschuh <linux@...ssschuh.net>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Mark Brown <broonie@...nel.org>, 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, srw@...dewatkins.net, rwarsow@....de, conor@...nel.org,
hargar@...rosoft.com, Willy Tarreau <w@....eu>
Subject: Re: [PATCH 6.15 000/780] 6.15.3-rc1 review
On 2025-06-18 15:19:11+0200, Greg Kroah-Hartman wrote:
> On Wed, Jun 18, 2025 at 12:58:00PM +0100, Mark Brown wrote:
> > On Tue, Jun 17, 2025 at 05:15:08PM +0200, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 6.15.3 release.
> > > There are 780 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.
> >
> > This breaks the build of the arm64 selftests due to a change in nolibc,
> > it appears that "tools/nolibc: properly align dirent buffer" is missing
> > some dependency:
> >
> > aarch64-linux-gnu-gcc -fno-asynchronous-unwind-tables -fno-ident -s -Os -nostdlib \
> > -include ../../../../include/nolibc/nolibc.h -I../..\
> > -static -ffreestanding -Wall za-fork.c /build/stage/build-work/kselftest/arm64/fp/za-fork-asm.o -o /build/stage/build-work/kselftest/arm64/fp/za-fork
> > In file included from ./../../../../include/nolibc/nolibc.h:107,
> > from <command-line>:
> > ./../../../../include/nolibc/dirent.h: In function ‘readdir_r’:
> > ./../../../../include/nolibc/dirent.h:62:64: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__nolibc_aligned_as’
> > 62 | char buf[sizeof(struct linux_dirent64) + NAME_MAX + 1] __nolibc_aligned_as(struct linux_dirent64);
> > | ^~~~~~~~~~~~~~~~~~~
> > ./../../../../include/nolibc/dirent.h:62:64: error: implicit declaration of function ‘__nolibc_aligned_as’ [-Wimplicit-function-declaration]
> > ./../../../../include/nolibc/dirent.h:62:84: error: expected expression before ‘struct’
> > 62 | char buf[sizeof(struct linux_dirent64) + NAME_MAX + 1] __nolibc_aligned_as(struct linux_dirent64);
> > | ^~~~~~
> > ./../../../../include/nolibc/dirent.h:63:47: error: ‘buf’ undeclared (first use in this function)
> > 63 | struct linux_dirent64 *ldir = (void *)buf;
> > | ^~~
> > ./../../../../include/nolibc/dirent.h:63:47: note: each undeclared identifier is reported only once for each function it appears in
>
> Thanks for the report, I'll go drop all nolibc patches from the queues
> for now.
Thanks.
Shouldn't the bots apply prerequisite patches from the series automatically?
This patch comes from [0] and the prerequisite is in there.
Also all nolibc patches which should go to stable are tagged as such.
Can you configure the bots not to pick up any nolibc patches automatically?
[0] https://lore.kernel.org/lkml/20250419-nolibc-ubsan-v2-0-060b8a016917@weissschuh.net/
Thomas
Powered by blists - more mailing lists