mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Schneider <pschneider1968@googlemail.com>
To: Sasha Levin <sashal@kernel.org>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	akpm@linux-foundation.org, torvalds@linux-foundation.org
Cc: 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 18:52:15 +0100	[thread overview]
Message-ID: <a4e5330c-5bd5-4262-a6eb-595ff01d1af6@googlemail.com> (raw)
In-Reply-To: <c435a3c6-5952-453f-9e50-31e0c6cdd09f@googlemail.com>


[-- Attachment #1.1: Type: text/plain, Size: 4320 bytes --]

Am 04.03.2026 um 18:27 schrieb Peter Schneider:
> 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:
> 
> 37f18915a261a arch/x86/kernel/setup.c    (Harshit Mogalapalli           2025-12-30 22:16:09 -0800  385)         ret = 
> ima_validate_range(ima_kexec_buffer_phys, ima_kexec_buffer_size);
> 37f18915a261a arch/x86/kernel/setup.c    (Harshit Mogalapalli           2025-12-30 22:16:09 -0800  386)         if (ret)
> 37f18915a261a arch/x86/kernel/setup.c    (Harshit Mogalapalli           2025-12-30 22:16:09 -0800  387) return ret;
> 37f18915a261a arch/x86/kernel/setup.c    (Harshit Mogalapalli           2025-12-30 22:16:09 -0800  388)
> 
> 
> which is this, now with a different commit SHA1: ( in [1] I found it was 73b97ee06bd635433d1c429ecdbc9167da5de588 )
> 
> 
> commit 37f18915a261afe84dab462624ed829cddb77a9b
> Author: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
> Date:   Tue Dec 30 22:16:09 2025 -0800
> 
>      x86/kexec: add a sanity check on previous kernel's ima kexec buffer
> 
>      [ Upstream commit c5489d04337b47e93c0623e8145fcba3f5739efd ]
> 
>      When the second-stage kernel is booted via kexec with a limiting command
>      line such as "mem=<size>", the physical range that contains the carried
>      over IMA measurement list may fall outside the truncated RAM leading to a
>      kernel panic.
> 
> 
> So, somehow this has come back between the new -rc2 and the release?!? But how and why? Did you retest this before the 
> release?
> 
> 
> Not good...
> 
> 
> [1] https://lore.kernel.org/stable/66461c13-1bb3-473c-b57f-adba9db4f756@googlemail.com/
> [2] https://lore.kernel.org/stable/a04b1aa6-ba46-4368-9dfe-6320a2dafa79@googlemail.com/



And it's also still (again?) in all the other 6.x stable branch releases of today:

6.6.128  22e460b6333a5
6.12.75  f8f73bf0f8a57
6.18.16  d4a132f121c59
6.19.6   4d7a8f5f28187

despite that you said in [1] that you dropped it. Strange...


[1] https://lore.kernel.org/stable/aaXSVaGrwY-k80m5@laps/


Beste Grüße,
Peter Schneider

-- 
Climb the mountain not to plant your flag, but to embrace the challenge,
enjoy the air and behold the view. Climb it so you can see the world,
not so the world can see you.                    -- David McCullough Jr.

OpenPGP:  0xA3828BD796CCE11A8CADE8866E3A92C92C3FF244
Download: https://www.peters-netzplatz.de/download/pschneider1968_pub.asc
https://keys.mailvelope.com/pks/lookup?op=get&search=pschneider1968@googlemail.com
https://keys.mailvelope.com/pks/lookup?op=get&search=pschneider1968@gmail.com

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  reply	other threads:[~2026-03-04 17:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-04 13:15 Sasha Levin
2026-03-04 13:15 ` Sasha Levin
2026-03-04 17:27 ` Peter Schneider
2026-03-04 17:52   ` Peter Schneider [this message]
2026-03-04 18:49     ` Peter Schneider
2026-03-04 19:20       ` Peter Schneider
2026-03-05  2:23   ` Sasha Levin

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=a4e5330c-5bd5-4262-a6eb-595ff01d1af6@googlemail.com \
    --to=pschneider1968@googlemail.com \
    --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=sashal@kernel.org \
    --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

all inboxes | Powered by JetHome®