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-=wjpXFOMq03cVq9XA+33QGALRzWV4mCND6dYpwAnXRqnmA@mail.gmail.com>
Date: Sat, 24 Aug 2024 10:22:54 +0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Bjorn Andersson <quic_bjorande@...cinc.com>
Cc: Will Deacon <will@...nel.org>, Bjorn Andersson <andersson@...nel.org>, 
	Catalin Marinas <catalin.marinas@....com>, linux-arm-kernel@...ts.infradead.org, 
	linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH] arm64: Allow packing uncompressed images into distro packages

On Sat, 24 Aug 2024 at 07:08, Bjorn Andersson <quic_bjorande@...cinc.com> wrote:
>
> But the change also made it possible to install "vmlinuz.efi", by
> setting both options to =y. Was this intentional?

Absolutely. My arm64 config in fact has EFI_ZBOOT enabled.

IOW, the intent of that CONFIG_COMPRESSED_INSTALL was simply to make
"make install" do the same thing that "make zinstall" used to do.

I in fact initially limited the whole COMPRESSED_INSTALL question to
be *only* for when EFI_ZBOOT is enabled (because that was my
situation), and privately asked Will if maybe non-EFI people want it.
So the patch originally had

+       depends on EFI && EFI_ZBOOT

and I asked Will

  Comments? Do the non-EFI_ZBOOT cases also perhaps want this (ie
  "Image.gz" as opposed to "vmlinuz.efi")?

  I intentionally tried to make it as limited as possible, but maybe the
  non-EFI people would want this too?

and he thought that it would be better to just make this compressed
install question be independent of anything else, and literally just
boil down to "do you want 'make install' to do the same thing as 'make
zinstall' does?"

I have *no* idea about what the actual package manager case wants, though.

              Linus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ