linux-kernel - Re: [PATCH 1/3] [RFC] genhd: add a new attribute in device structure

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: <1308320844.2586.14.camel@mulgrave>
Date:	Fri, 17 Jun 2011 10:27:24 -0400
From:	James Bottomley <James.Bottomley@...senPartnership.com>
To:	Kay Sievers <kay.sievers@...y.org>
Cc:	Greg KH <greg@...ah.com>,
	Nao Nishijima <nao.nishijima.xt@...achi.com>,
	linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org,
	jcm@...hat.com, hare@...e.de, stefanr@...6.in-berlin.de,
	yrl.pp-manager.tt@...achi.com
Subject: Re: [PATCH 1/3] [RFC] genhd: add a new attribute in device
 structure

On Fri, 2011-06-17 at 01:04 +0200, Kay Sievers wrote:
> >> We need many names, and we need all of them from the very
> beginning,
> >> and they should not change during device lifetime unless the device
> >> state changes.
> >
> > So that's actually an argument for leaving the links, surely?  We
> can
> > have many inbound links, but the kernel can only print one name in
> > messages, which would be the preferred name that was currently set.
> 
> I really question any concept of _the_ name. My take on it: It will
> never work in reality. 

OK, so lets take the common example: a desktop with three disks and an
enclosure with three slots and labels "fred", "jim", and "betty".

The desired outcome is that whenever the user manipulates those devices
he uses a name related to the label, so whenever dmesg flags a problem,
it says sd betty:  device offline or something.  Whenever he mounts, he
mounts by /dev/disk/by-preferred/betty (or whatever the current udev
vernacular is).  Whenever smartmon says there's an over temp problem. it
says that fred has it;  cat /proc/partitions shows how fred, jim and
betty are partitioned and so on.

To do this, we set the preferred name at start of day via a machine
specific customisation.  For an enclosure, there's a standard way of
mapping the name to the device, so we'd just use that, but it's not
impossible to imagine systems with stranger entities that require per
motherboard customisations.

Once the name is set in boot up, we, in fact, never alter it.

With the kernel patch proposed and a corresponding update to udev
actually makes all the above happen.  There have to be tweaks to the
startup scripts, like smartd needs a file configuration that lists the
disk by preferred path so that the output is correct.

Obviously, I chose the commands above so there is no need to modify any
of them.  There will be utilities (like overly smart san managers) that
do derive the name and will need updating, but they're not among the
standard workstation admin tools.

James

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