linux-kernel - Re: root=PARTUUID for MBR/NT disk signatures?

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: <20120820182254.GQ24861@google.com>
Date:	Mon, 20 Aug 2012 11:22:54 -0700
From:	Tejun Heo <tj@...nel.org>
To:	Stephen Warren <swarren@...dotorg.org>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Will Drewry <wad@...omium.org>,
	"cross-distro@...ts.linaro.org" <cross-distro@...ts.linaro.org>,
	Jens Axboe <axboe@...nel.dk>,
	Kay Sievers <kay.sievers@...y.org>
Subject: Re: root=PARTUUID for MBR/NT disk signatures?

Hello,

On Fri, Aug 17, 2012 at 04:10:52PM -0600, Stephen Warren wrote:
> 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?

Wouldn't that be able to break setups which work currently?

Thanks.

-- 
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/