From: Sasha Levin <sashal@kernel.org>
To: Peter Schneider <pschneider1968@googlemail.com>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
akpm@linux-foundation.org, torvalds@linux-foundation.org,
lwn@lwn.net, jslaby@suse.cz, gregkh@linuxfoundation.org,
Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
Subject: Re: Linux 6.1.165
Date: Wed, 4 Mar 2026 21:23:13 -0500 [thread overview]
Message-ID: <aajpEdVsMnl61S_O@laps> (raw)
In-Reply-To: <c435a3c6-5952-453f-9e50-31e0c6cdd09f@googlemail.com>
On Wed, Mar 04, 2026 at 06:27:00PM +0100, Peter Schneider wrote:
>Hi Sasha,
>
>
>Am 04.03.2026 um 14:15 schrieb Sasha Levin:
>>I'm announcing the release of the 6.1.165 kernel.
>>
>>All users of the 6.1 kernel series must upgrade.
>>
>>The updated 6.1.y git tree can be found at:
>> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-6.1.y
>>and can be browsed at the normal kernel.org git web browser:
>> https://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
>>
>>
>>Thanks,
>>Sasha
>
>
>In the now released 6.1.165, I get the same build error as I have reported in the 1st incarnation of 6.1.165-rc2 (see [1])
>
> CC arch/x86/kernel/setup.o
>arch/x86/kernel/setup.c: In function ‘ima_get_kexec_buffer’:
>arch/x86/kernel/setup.c:385:15: error: implicit declaration of
>function ‘ima_validate_range’ [-Wimplicit-function-declaration]
> 385 | ret = ima_validate_range(ima_kexec_buffer_phys, ima_kexec_buffer_size);
> | ^~~~~~~~~~~~~~~~~~
>make[3]: *** [scripts/Makefile.build:250: arch/x86/kernel/setup.o] Fehler 1
>make[2]: *** [scripts/Makefile.build:503: arch/x86/kernel] Fehler 2
>make[1]: *** [scripts/Makefile.build:503: arch/x86] Fehler 2
>make: *** [Makefile:2025: .] Fehler 2
>root@linus:/usr/src/linux-stable# git status
>HEAD losgelöst bei v6.1.165
>
>
>So the offending patch seems to be still in, although in the 2nd
>incarnation of -rc2 which you force pushed over the 1st one of -rc2,
>it was then reverted after my report [2]. When i git blame
>arch/x86/kernel/setup.c and look at the offending line I see:
Yup, sorry. I don't have as much automation as Greg does, so many of the steps
were manual...
--
Thanks,
Sasha
prev parent reply other threads:[~2026-03-05 2:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 13:15 Linux 6.1.165 Sasha Levin
2026-03-04 13:15 ` Sasha Levin
2026-03-04 17:27 ` Peter Schneider
2026-03-04 17:52 ` Peter Schneider
2026-03-04 18:49 ` Peter Schneider
2026-03-04 19:20 ` Peter Schneider
2026-03-05 2:23 ` Sasha Levin [this message]
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=aajpEdVsMnl61S_O@laps \
--to=sashal@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=harshit.m.mogalapalli@oracle.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=pschneider1968@googlemail.com \
--cc=stable@vger.kernel.org \
--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