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] [day] [month] [year] [list]
Message-Id: <20220327083854.5f44f9a33a21c53a410ff6db@kernel.org>
Date:   Sun, 27 Mar 2022 08:38:54 +0900
From:   Masami Hiramatsu <mhiramat@...nel.org>
To:     Masami Hiramatsu <mhiramat@...nel.org>
Cc:     Steven Rostedt <rostedt@...dmis.org>,
        Padmanabha Srinivasaiah <treasure4paddy@...il.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org,
        Randy Dunlap <rdunlap@...radead.org>
Subject: Re: [PATCH v4 0/3] bootconfig: Support embedding a bootconfig in
 kernel for non initrd boot

Hi,

I forgot to add LTO people and Masahiro to this mail. Let me update the
cover mail and resubmit.

On Sun, 27 Mar 2022 08:36:53 +0900
Masami Hiramatsu <mhiramat@...nel.org> wrote:

> Hi,
> 
> Here are the 4th version of the patchset to enable kernel embedded bootconfig
> for non-initrd kernel boot environment. I've fixed Makefile to determine
> update by checking the contents of embedding bootconfig file. Thanks
> Masahiro!
> 
> You can embed a bootconfig file into the kernel as a default bootconfig,
> which will be used if there is no initrd or no bootconfig is attached to initrd. 
> 
> This needs 2 options: CONFIG_EMBED_BOOT_CONFIG=y and set the file
> path to CONFIG_EMBED_BOOT_CONFIG_FILE. Even if you embed the bootconfig file
> to the kernel, it will not be enabled unless you pass "bootconfig" kernel
> command line option at boot. Moreover, since this is just a "default"
> bootconfig, you can override it with a new bootconfig if you attach another
> bootconfig to the initrd (if possible).
> CONFIG_EMBED_BOOT_CONFIG_FILE can take both absolute and relative path, but
> to simplify and make it independent from the build environment, I recommend
> you to use an absolute path for that.
> 
> This is requested by Padmanabha at the below thread;
> 
>  https://lore.kernel.org/all/20220307184011.GA2570@pswork/T/#u
> 
> Thank you,
> 
> ---
> 
> Masami Hiramatsu (3):
>       bootconfig: Check the checksum before removing the bootconfig from initrd
>       bootconfig: Support embedding a bootconfig file in kernel
>       docs: bootconfig: Add how to embed the bootconfig into kernel
> 
> 
>  Documentation/admin-guide/bootconfig.rst |   30 ++++++++++++++++++++++++++---
>  include/linux/bootconfig.h               |   10 ++++++++++
>  init/Kconfig                             |   21 ++++++++++++++++++++
>  init/main.c                              |   31 +++++++++++++++---------------
>  lib/.gitignore                           |    1 +
>  lib/Makefile                             |   10 ++++++++++
>  lib/bootconfig.c                         |   23 ++++++++++++++++++++++
>  7 files changed, 108 insertions(+), 18 deletions(-)
> 
> --
> Masami Hiramatsu (Linaro) <mhiramat@...nel.org>


-- 
Masami Hiramatsu <mhiramat@...nel.org>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ