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

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

Message-ID: <20160814090914.GA24011@amd>
Date:	Sun, 14 Aug 2016 11:09:15 +0200
From:	Pavel Machek <pavel@....cz>
To:	james harvey <jamespharvey20@...il.com>
Cc:	kernel list <linux-kernel@...r.kernel.org>
Subject: Re: Who reordered my disks (probably v4.8-rc1 problem)

Hi!

> 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.

> 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.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html