From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Mark Brown <broonie@kernel.org>,
stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org, hargar@microsoft.com, Willy Tarreau <w@1wt.eu>
Subject: Re: [PATCH 6.15 000/780] 6.15.3-rc1 review
Date: Thu, 19 Jun 2025 06:19:52 +0200 [thread overview]
Message-ID: <2025061949-epilepsy-punk-fb4e@gregkh> (raw)
In-Reply-To: <1081af30-1273-4a9a-a864-f59f1cb54fd1@t-8ch.de>
On Wed, Jun 18, 2025 at 04:15:09PM +0200, Thomas Weißschuh wrote:
> 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?
Hopefully yes, obviously it doesn't always work :)
> 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?
Yes we can! I will add the needed regex to the file:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/ignore_list
should it be:
tools/include/nolibc/*
tools/testing/selftests/nolibc/*
?
thanks,
greg k-h
next prev parent reply other threads:[~2025-06-19 4:19 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 15:15 Greg Kroah-Hartman
2025-06-17 15:22 ` [PATCH 6.15 468/780] perf symbol: Fix use-after-free in filename__read_build_id Greg Kroah-Hartman
2025-06-17 16:12 ` [PATCH 6.15 000/780] 6.15.3-rc1 review Christian Heusel
2025-06-17 16:49 ` Florian Fainelli
2025-06-17 18:27 ` Ronald Warsow
2025-06-17 21:10 ` Luna Jernberg
2025-06-18 5:42 ` Greg Kroah-Hartman
2025-06-18 13:32 ` Pascal Ernster
[not found] ` <20250617152521.879529420@linuxfoundation.org>
[not found] ` <04b7faf5-2f69-4d02-9eca-916e4bffcf00@gmx.de>
2025-06-18 19:58 ` Pascal Ernster
2025-06-18 20:31 ` Pascal Ernster
2025-06-19 4:17 ` Greg Kroah-Hartman
2025-06-21 22:09 ` Pascal Ernster
2025-06-22 7:24 ` Greg Kroah-Hartman
2025-06-17 21:17 ` Shuah Khan
2025-06-18 5:51 ` Achill Gilgenast
2025-06-18 6:19 ` Ron Economos
2025-06-18 6:42 ` Jon Hunter
2025-06-18 8:11 ` Takeshi Ogasawara
2025-06-18 8:35 ` Peter Schneider
2025-06-18 10:38 ` Naresh Kamboju
2025-06-18 11:58 ` Mark Brown
2025-06-18 13:19 ` Greg Kroah-Hartman
2025-06-18 14:15 ` Thomas Weißschuh
2025-06-19 4:19 ` Greg Kroah-Hartman [this message]
2025-06-19 5:50 ` Thomas Weißschuh
2025-06-19 8:20 ` Greg Kroah-Hartman
2025-06-18 12:59 ` Miguel Ojeda
2025-06-18 18:07 ` Hardik Garg
2025-06-19 1:36 ` Justin Forbes
2025-06-19 4:05 ` Greg Kroah-Hartman
2025-06-19 4:06 ` Greg Kroah-Hartman
2025-06-23 21:05 ` Naresh Kamboju
2025-06-24 10:15 ` Greg Kroah-Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2025061949-epilepsy-punk-fb4e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=hargar@microsoft.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=linux@weissschuh.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=w@1wt.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®