From: Sasha Levin <sashal@kernel.org>
To: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
Cc: Peter Schneider <pschneider1968@googlemail.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
gregkh@linuxfoundation.org, patches@lists.linux.dev,
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.1 000/533] 6.1.165-rc2 review
Date: Mon, 2 Mar 2026 12:49:50 -0500 [thread overview]
Message-ID: <aaXNvoIGNjR86bKY@laps> (raw)
In-Reply-To: <7cfc1cde-a8e1-4802-831c-3e082b22fa73@oracle.com>
On Mon, Mar 02, 2026 at 11:06:17PM +0530, Harshit Mogalapalli wrote:
>Hi Sasha,
>
>On 02/03/26 22:56, Peter Schneider wrote:
>>Am 02.03.2026 um 17:09 schrieb Sasha Levin:
>>>
>>>This is the start of the stable review cycle for the 6.1.165 release.
>>>There are 533 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.
>>
>>
>>I get a build error in arch/x86/kernel/setup.c:
>>
>> 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-rc#
>>
>>
>>I always do my test builds with CONFIG_WEROR=Y, full .config attached.
>>
>>The line causing the error seems to come from
>>
>>73b97ee06bd63 x86/kexec: add a sanity check on previous kernel's ima
>>kexec buffer [ Upstream commit
>>c5489d04337b47e93c0623e8145fcba3f5739efd ]
>>
>
>Interesting: I didn't get an email that this got queued to 6.1.165,
>note: this is not in 6.1.165-rc1, but in 6.1.165-rc2.
>
>I only got: FAILED: Patch "x86/kexec: add a sanity check on previous
>kernel's ima kexec buffer" failed to apply to 6.1-stable tree
>
>In any case: we need a prerequisite for this, so I will work on
>backports in a few days, I think for now, we should drop this commit
>from 6.1.y.
>
>Also I see something unusual -->
>
>6.1.165-rc1 --> 232 patches.
>
>6.1.165-rc2 --> 533 patches.
>
>Can you please check ?
That's the reason for -rc2 :) See:
https://lore.kernel.org/all/aaWWE5uQqz_eG69i@laps/
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-03-02 17:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 16:09 [PATCH 6.1 000/533] 6.1.165-rc2 review Sasha Levin
2026-03-02 17:26 ` Peter Schneider
2026-03-02 17:36 ` Harshit Mogalapalli
2026-03-02 17:49 ` Sasha Levin [this message]
2026-03-02 17:58 ` Harshit Mogalapalli
2026-03-02 18:07 ` Sasha Levin
2026-03-02 17:48 ` Sasha Levin
2026-03-02 17:57 ` Peter Schneider
2026-03-02 18:09 ` Sasha Levin
2026-03-02 18:15 ` Peter Schneider
2026-03-02 19:46 ` Brett A C Sheffield
2026-03-02 20:12 ` Peter Schneider
2026-03-02 19:35 ` Brett A C Sheffield
2026-03-02 19:55 ` Peter Schneider
2026-03-03 4:52 ` Florian Fainelli
2026-03-03 7:34 ` Francesco Dolcini
2026-03-03 12:26 ` Ron Economos
2026-03-03 14:12 ` Jon Hunter
2026-03-03 19:37 ` Mark Brown
2026-03-03 21:18 ` Miguel Ojeda
2026-03-04 6:14 ` Hardik Garg
2026-03-04 17:47 ` Shuah Khan
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=aaXNvoIGNjR86bKY@laps \
--to=sashal@kernel.org \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hargar@microsoft.com \
--cc=harshit.m.mogalapalli@oracle.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