From: "Linux regression tracking #update (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Linux regressions mailing list <regressions@lists.linux.dev>
Cc: Dave Young <dyoung@redhat.com>, Ard Biesheuvel <ardb@google.com>,
Kees Cook <keescook@chromium.org>, Aaron Lu <aaron.lu@intel.com>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Borislav Petkov <bp@alien8.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kexec@lists.infradead.org, Tom Lendacky <thomas.lendacky@amd.com>,
x86@kernel.org
Subject: Re: kexec reboot failed due to commit 75d090fd167ac
Date: Fri, 22 Sep 2023 12:12:44 +0200 [thread overview]
Message-ID: <08a432e0-4e16-41a6-bad6-e6a51ea34a97@leemhuis.info> (raw)
In-Reply-To: <20230921160325.g5ei2gfads6deb32@box.shutemov.name>
On 21.09.23 18:03, Kirill A. Shutemov wrote:
> On Thu, Sep 21, 2023 at 11:54:15AM +0200, Linux regression tracking (Thorsten Leemhuis) wrote:
>> On 13.09.23 16:24, Kirill A. Shutemov wrote:
>>> On Mon, Sep 11, 2023 at 05:57:07PM +0300, Kirill A. Shutemov wrote:
>>>> On Mon, Sep 11, 2023 at 10:56:36PM +0800, Dave Young wrote:
>>>>>> early console in extract_kernel
>>>>>> input_data: 0x000000807eb433a8
>>>>>> input_len: 0x0000000000d26271
>>>>>> output: 0x000000807b000000
>>>>>> output_len: 0x0000000004800c10
>>>>>> kernel_total_size: 0x0000000003e28000
>>>>>> needed_size: 0x0000000004a00000
>>>>>> trampoline_32bit: 0x000000000009d000
>>>>>>
>>>>>> Decompressing Linux... out of pgt_buf in arch/x86/boot/compressed/ident_map_64.c!?
>>>>>> pages->pgt_buf_offset: 0x0000000000006000
>>>>>> pages->pgt_buf_size: 0x0000000000006000
>>>>>>
>>>>>> Error: kernel_ident_mapping_init() failed
>>> [...]
>>>> The problem is not limited to unaccepted memory, it also triggers if we
>>>> reach efi_get_rsdp_addr() in the same setup.
>>>>
>>>> I think we have several problems here.
>>> [...]
>>>> Any comments?
>>>
>>> I struggle to come up with anything better than increasing the constant to
>>> a value that "ought to be enough for anybody" ©, let's say 128K.
>>>
>>> And we can eliminate logic on no-KASLR vs. KASLR vs. KASLR+VERBOSE_BOOTUP.
>>>
>>> Objections?
>>
>> Apparently not, as there was no reply since then (which is why I show up
>> here, as it looked like fixing this regression stalled).
>
> It has been fixed in upstream by the commit f530ee95b72e
> ("x86/boot/compressed: Reserve more memory for page tables")
Ahh, great, thx for letting me know. That commit sadly missed a Link: or
Closes: tag to the regression report, which Linus and the docs ask for
(and regression tracking relies on), then it would have noticed this
automatically. Whatever, things happen, thx again.
#regzbot fix: f530ee95b72e
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.
prev parent reply other threads:[~2023-09-22 10:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 11:48 Aaron Lu
2023-08-29 12:14 ` Bagas Sanjaya
2023-08-29 12:51 ` Aaron Lu
2023-08-29 12:59 ` Kirill A. Shutemov
2023-08-29 14:04 ` Aaron Lu
2023-09-07 13:14 ` Kirill A. Shutemov
2023-09-08 6:02 ` Aaron Lu
2023-09-08 12:32 ` Kirill A. Shutemov
2023-09-08 15:58 ` Kees Cook
2023-09-08 16:17 ` Ard Biesheuvel
2023-09-09 11:32 ` Kirill A. Shutemov
2023-09-11 14:56 ` Dave Young
2023-09-11 14:57 ` Kirill A. Shutemov
2023-09-11 15:33 ` Tom Lendacky
2023-09-11 15:53 ` Kirill A. Shutemov
2023-09-11 17:13 ` Tom Lendacky
2023-09-13 14:24 ` Kirill A. Shutemov
2023-09-21 9:54 ` Linux regression tracking (Thorsten Leemhuis)
2023-09-21 16:03 ` Kirill A. Shutemov
2023-09-22 10:12 ` Linux regression tracking #update (Thorsten Leemhuis) [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=08a432e0-4e16-41a6-bad6-e6a51ea34a97@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=aaron.lu@intel.com \
--cc=ardb@google.com \
--cc=bagasdotme@gmail.com \
--cc=bp@alien8.de \
--cc=dyoung@redhat.com \
--cc=keescook@chromium.org \
--cc=kexec@lists.infradead.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=thomas.lendacky@amd.com \
--cc=x86@kernel.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®