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: <20160814123850.GA10884@gherkin.frus.com>
Date:	Sun, 14 Aug 2016 07:38:50 -0500
From:	Bob Tracy <rct@...rkin.frus.com>
To:	james harvey <jamespharvey20@...il.com>
Cc:	Pavel Machek <pavel@....cz>,
	kernel list <linux-kernel@...r.kernel.org>
Subject: Re: Who reordered my disks (probably v4.8-rc1 problem)

On Sun, Aug 14, 2016 at 05:03:33AM -0400, james harvey 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

The key takeaway from the above is, for the non-GPT case, userspace
support (blkid and friends) is required to take advantage of static
(persistent) naming, i.e., an initial ramdisk of some kind is no
longer optional (boo! hiss!).

There's an implied requirement for udev as well, but that's not nearly
as distasteful.  I had to make my peace with udev on an otherwise
primitive (simple) Slackware system a few years ago when I upgraded my
system hardware: included was a sound device with an HDMI interface,
and the associated ALSA driver only supported dynamic minor devices.

--Bob