From: Steven Rostedt <rostedt@goodmis.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Alistair Delva <adelva@google.com>,
linux-doc@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] bootconfig: Add value override operator
Date: Wed, 15 Jul 2020 20:02:12 -0400 [thread overview]
Message-ID: <20200715200212.0db61d5a@oasis.local.home> (raw)
In-Reply-To: <20200716073843.e7b1921aae962da9e5714fe0@kernel.org>
On Thu, 16 Jul 2020 07:38:43 +0900
Masami Hiramatsu <mhiramat@kernel.org> wrote:
> > So the end of the initrd would have:
> >
> > [data][size/checksum/magic][more-data][size/checksum/magic]
> >
> >
> > And the kernel could do the following:
> >
> > 1. read the end of the initrd for bootconfig
> > 2. If found parse the bootconfig data.
> > 3. look at the content before the bootconfig
> > 4. if another bootconfig exists, goto 2.
> >
>
> Yeah, that is possible. But since the total size of the bootconfig
> is limited to 32KB (this means data + 1st footer + more-data),
> I would like to give a chance of sanity check to the bootloader.
That's a limit of the size field, right?
The bootloader (and all tools including the kernel) could check for
multiple instances, and that would even increase the size of what can
be added. As each section would be 32KB max size, but there's no limit
to how many you have. All tools, bootconfig, the bootloader, and the
kernel can perform the checksum.
-- Steve
next prev parent reply other threads:[~2020-07-16 0:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 16:00 [PATCH 0/3] bootconfig: Add value override operator Masami Hiramatsu
2020-07-15 16:00 ` [PATCH 1/3] lib/bootconfig: Add override operator support Masami Hiramatsu
2020-07-15 16:00 ` [PATCH 2/3] tools/bootconfig: Add testcases for value override operator Masami Hiramatsu
2020-07-15 16:00 ` [PATCH 3/3] Documentation: bootconfig: Add bootconfig " Masami Hiramatsu
2020-07-15 20:45 ` [PATCH 0/3] bootconfig: Add value " Steven Rostedt
2020-07-15 22:38 ` Masami Hiramatsu
2020-07-16 0:02 ` Steven Rostedt [this message]
2020-07-16 1:27 ` Masami Hiramatsu
2020-07-30 0:56 ` Masami Hiramatsu
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=20200715200212.0db61d5a@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=adelva@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@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;
as well as URLs for NNTP newsgroup(s).