linux-kernel - Re: Who reordered my disks (probably v4.8-rc1 problem)

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: <CA+X5Wn6Qm36CuEw7DJX90XsA4tBeKSLHe7RupjAyEiAKSuhzLQ@mail.gmail.com>
Date:	Sun, 14 Aug 2016 17:40:09 -0400
From:	james harvey <jamespharvey20@...il.com>
To:	Pavel Machek <pavel@....cz>
Cc:	kernel list <linux-kernel@...r.kernel.org>
Subject: Re: Who reordered my disks (probably v4.8-rc1 problem)

On Sun, Aug 14, 2016 at 5:09 AM, Pavel Machek <pavel@....cz> wrote:
>> Use static (persistent) naming instead, /dev/disk/by-label,
>> /dev/disk/by-id, /dev/disk/by-uuid, and if gpt /dev/disk/by-partlabel
>> and /dev/disk/by-partuuid
>
> Explain that to my bootloader. Kernel needs root= on a command line.

It does need a root parameter.  Use root=PARTUUID=<partition UUID>.
Note the UUID is the PARTUUID from "blkid" which is for the partition,
not the UUID field which is for the filesystem.


>> As you found, /dev/sdX bus names are assigned in the order they are
>> added, which for some time has not been guaranteed to remain
>> consistent between kernel versions or even subsequent boots on the
>> same kernel.
>
> Well, for usb, order is not guaranteed, for SATA, it worked. So that's
> a regression in v4.8-rc1.
>
> Yes, /dev/disk/by-* is good idea, but this broke my boot, probably
> broke some scripts that used for a long time... and kernel may not
> break working systems.

It's always possible others may disagree, but I don't think something
is a regression when what breaks has long been said to not be expected
to work.