From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Peter Schneider <pschneider1968@googlemail.com>
Cc: 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@nabladev.com, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, rwarsow@gmx.de, conor@kernel.org,
hargar@microsoft.com, broonie@kernel.org, achill@achill.org,
sr@sladewatkins.com
Subject: Re: [PATCH 6.18 000/333] 6.18.19-rc1 review
Date: Wed, 18 Mar 2026 12:53:52 +0100 [thread overview]
Message-ID: <2026031840-moody-liftoff-bcf9@gregkh> (raw)
In-Reply-To: <731ff34b-3967-4a21-83e4-d85009c48f1c@googlemail.com>
On Tue, Mar 17, 2026 at 10:03:40PM +0100, Peter Schneider wrote:
> Am 17.03.2026 um 17:30 schrieb Greg Kroah-Hartman:
> > This is the start of the stable review cycle for the 6.18.19 release.
> > There are 333 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.
>
>
> Same build failure as in 6.19.9-rc1 on my 2-socket Ivy Bridge Xeon E5-2697 v2 server:
>
> LD vmlinux.unstripped
> BTFIDS vmlinux.unstripped
> WARN: resolve_btfids: unresolved symbol kthread_exit
>
> and git revert 0507972c8244d6454cbfd242157e86bb01971bf2 (kthread:
> consolidate kthread exit paths to prevent use-after-free) makes the build
> error go away, but may keep the original bug the patch intended to fix?!
> Wentao Guan wrote in [1] that an additional backport is needed to make this
> patch work, but I didn't test this...
>
> Tested-by: Peter Schneider <pschneider1968@googlemail.com>
>
>
> [1] https://lore.kernel.org/stable/20260317175812.707723-1-guanwentao@uniontech.com/
I've queued up a fix for this and will push out a -rc2 soon.
thanks,
greg k-h
next prev parent reply other threads:[~2026-03-18 11:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 16:30 Greg Kroah-Hartman
2026-03-17 20:17 ` Brett A C Sheffield
2026-03-17 21:03 ` Peter Schneider
2026-03-18 11:53 ` Greg Kroah-Hartman [this message]
2026-03-18 0:45 ` Miguel Ojeda
2026-03-18 6:49 ` Jeffrin Thalakkottoor
2026-03-18 7:16 ` Shung-Hsi Yu
2026-03-18 8:17 ` Jon Hunter
2026-03-18 9:03 ` Ron Economos
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=2026031840-moody-liftoff-bcf9@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=achill@achill.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=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@nabladev.com \
--cc=pschneider1968@googlemail.com \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=sr@sladewatkins.com \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.org \
/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®