mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Will Drewry <wad@chromium.org>,
	"cross-distro@lists.linaro.org" <cross-distro@lists.linaro.org>,
	Jens Axboe <axboe@kernel.dk>, Tejun Heo <tj@kernel.org>,
	Kay Sievers <kay.sievers@vrfy.org>
Subject: root=PARTUUID for MBR/NT disk signatures?
Date: Fri, 17 Aug 2012 16:10:52 -0600	[thread overview]
Message-ID: <502EC16C.4030007@wwwdotorg.org> (raw)

I was considering extending the kernel command-line option
root=PARTUUID= to also support MBR (NT disk signatures). I was thinking
of a syntax along the lines of:

root=PARTUUID=UUUUUUUU-PP[/PARTNROFF=%d]

... where UUUUUUUU is the hex representation of the NT disk signature,
and PP is the hex representation of the partition number. Like GPT,
/PARTNROFF could be used too if desired.

Related, I was thinking of changing struct partition_meta_info's uuid
field to be a string, so that it could simply be strcmp'd against the
UUID value on the kernel command-line. That way, the type of the UUID is
irrelevant.

Does anyone have any objection to that?

The reason I aim for that syntax rather than say:

root=MBRSIG=UUUUUUUU-PP[/PARTNROFF=%d]

... is to allow boot-loaders (e.g. U-Boot on ARM) to store just the
partition ID in a variable, and prepend all the Linux-specific stuff on
the front, e.g.

# For GPT:
setenv kernel_part_uuid b2f82cda-2535-4779-b467-094a210fbae7
# For MBR:
setenv kernel_part_uuid UUUUUUUU-PP

In fact, those hard-coded statements would probably be replaced with a
run-time command:

part uuid mmc 0:1 kernel_part_uuid

# Then in a common script:
setenv bootargs root=PARTUUID=${kernel_part_uuid}

Otherwise, the value of the uuid variable (or result of the "part uuid"
command) would need to prepend the PARTUUID= or MBRSIG= to the "uuid"
variable's value, and that's probably Linux-specific rather than part of
a generic UUID for the partition.

             reply	other threads:[~2012-08-17 22:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-17 22:10 Stephen Warren [this message]
2012-08-20 18:22 ` Tejun Heo
2012-08-20 18:30   ` Stephen Warren
2012-08-21  4:47     ` Will Drewry
2012-08-21  6:38       ` Michael Tokarev
2012-08-21 18:08       ` Stephen Warren
2012-08-21 18:47         ` Will Drewry

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=502EC16C.4030007@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=axboe@kernel.dk \
    --cc=cross-distro@lists.linaro.org \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@kernel.org \
    --cc=wad@chromium.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

Powered by JetHome