linux-kernel - Re: [for-next][PATCH 04/26] bootconfig: Add Extra Boot Config support

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20200211001007.62290c743e049b231bdd7052@kernel.org>
Date:   Tue, 11 Feb 2020 00:10:07 +0900
From:   Masami Hiramatsu <mhiramat@...nel.org>
To:     Borislav Petkov <bp@...en8.de>
Cc:     Steven Rostedt <rostedt@...dmis.org>, linux-kernel@...r.kernel.org,
        Ingo Molnar <mingo@...nel.org>,
        Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [for-next][PATCH 04/26] bootconfig: Add Extra Boot Config
 support

On Mon, 10 Feb 2020 12:25:13 +0100
Borislav Petkov <bp@...en8.de> wrote:

> On Sat, Feb 08, 2020 at 12:06:48AM +0900, Masami Hiramatsu wrote:
> > OK, could you tell me your idea to make it better? I'm waiting for such
> > discussion a half of last year :)
> 
> Yah, situation sounds familiar. :)
> 
> > For your information, here is the background of this bootconfig.
> > To build my boot-time tracing, I need a way to pass a flexible and
> > structured configuration at boot time.
> 
> Can I see an actual example of what you're doing?

Sure, there are some examples under Documentation/trace/boottime-trace.rst.
Since the tracefs (ftrace's filesystem user interface) is extensible
by dynamic events and instanses, I need flexibility of option "keys"
not only values, also I need structured settings because some keys
will configure same events or trace instance.
For example, ftrace has tracing instances (which represents different
trace logs) which has some set of configuration parameters. Some
parameters has sub-parameters (trace options), and most parameters
have default parameters. I don't want to make it a single parametarized
options, like ftrace.instance="NAME:OPT1,OPT2:CLOCK:SIZE:SNAPSHOT:...",
because it is not human readable and easy to make mistakes.
Instead, bootconfig solve that with structured, multi-line keys;

ftrace.instance.NAME {
	options = OPT1,OPT2
	trace_clock = CLOCK
	buffer_size = SIZE
	...
}

If we have 3 or more instances, it is easy to expand it as

ftrace.instance {
	NAME1 {
		...
	}
	NAME2 {
		...
	}
	NAME3 {
		...
	}
}

(Hmm, maybe I should reserve "default" name for setting a default configuration)

> > I had tried to reuse devicetree at first, but it was rejected because
> > the devicetree is only for describing hardware. So I introduced this
> > bootconfig.
> 
> Makes sense.
> 
> > When I designed the bootconfig, I tried to sort out the requirements.
> > That config should be able to pass all setting we can do on tracefs.
> > Since ftrace already has a parser for tracefs, we don't need any types
> > for each settings. Thus it should be something like sysctl.conf. But the
> > sysctl.conf was too simple, it couldn't handle several related keys
> > well. So I decided to introduce braces which put together some related
> > parameters. And the bootconfig syntax was born.
> 
> Ok, here's my boot command line:
> 
> [    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.5.0-rc7+ root=/dev/nvme0n1p2 ro root=/dev/disk/by-id/nvme-eui.0025385481b2fe2a-part2 resume=/dev/disk/by-id/nvme-eui.0025385481b2fe2a-part1 debug ignore_loglevel log_buf_len=16M no_console_suspend net.ifnames=0 mem_encrypt=off systemd.log_target=null
> 
> How do I use the bootconfig thing with it? Or is it not supposed to be
> used that way? IOW, how is it supposed to be used so that it needs to be
> enabled on every box?

Sure,

1) write a following bootconfig file
----
kernel {
	# root device and resume devices
	root = /dev/disk/by-id/nvme-eui.0025385481b2fe2a-part2
	resume = /dev/disk/by-id/nvme-eui.0025385481b2fe2a-part1
	ro			# Mount root device readonly.
	debug			# boot with debug log
	ignore_loglevel	# this will print all messages
	log_buf_len = 16M	# So expand log buffer to 16MB
	no_console_suspend	# Debugging suspend process
	mem_encrypt = off	# Set AMD SME to off
}

init {
	net.ifnames = 0	# Use tradisional ifname
	systemd.log_target = null	# Ignore systemd log?
}
----
2) Use tools/bootconfig/bootconfig to apply it to your initrd image
# tools/bootconfig/bootconfig -a <your-bootconfig> <your-initrd>
3) boot.

Note that I don't intended to "replace" all legacy command line
(but it is easy for bootloaders to use bootconfig) it seems above example
seems have some options which added by the bootloader.

> 
> > Okay, I hope it and try to prove it. Anyway, to use boot-time tracing which
> > can fully utilize ftrace at boot-time, we have to enable bootconfig.
> 
> Ok, this is getting closer. But not everyone is using boottime tracing?

No, (but I HOPE so). 

> 
> Or is the logic: every user/tool might need to be able to do boottime
> tracing at some future point in time and bootconfig is a mandatory part
> of that use case?

Boot time tracing is just a example. I think we can expand this for some
other subsystems too. And this might be also helpful for adding a bit more
complex syntax to those parameters without parser.

Thank you,

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