linux-kernel - Re: [v2] arm64: Rename to KERNEL_IMAGE_COMPRESSED_INSTALL kconfig for compressed kernel image

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHk-=wiruM9sWeOM8FKvGTetiWgSaGZF31YmdzS3_s=0bw0Ekg@mail.gmail.com>
Date: Fri, 26 Jul 2024 14:47:47 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: sedat.dilek@...il.com
Cc: Catalin Marinas <catalin.marinas@....com>, Will Deacon <will@...nel.org>, 
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [v2] arm64: Rename to KERNEL_IMAGE_COMPRESSED_INSTALL kconfig for
 compressed kernel image

On Fri, 26 Jul 2024 at 13:54, Sedat Dilek <sedat.dilek@...il.com> wrote:
>
> And when you check a diff of two of your ARM64 .config?
> What says COMPRESSED_INSTALL to other than the author w/o context :-)?

Even without any context, I think it says "compressed install".

Which seems sensible. Because THAT'S EXACTLY WHAT IT IS.

Now, admittedly I would have preferred not having a config option for
this at all, but we have a sad historical situation of doing something
odd on arm (and parisc).

The RISC-V people used to do the same, but they decided to just make
'install' do whatever image was built, so they base it on a
combination of different config variables: CONFIG_XIP_KERNEL,
CONFIG_RISCV_M_MODE, CONFIG_SOC_CANAAN_K210, and CONFIG_EFI_ZBOOT.

I considered just using our pre-existing CONFIG_EFI_ZBOOT variable,
but without knowing what the different boot loaders do...

               Linus