linux-kernel - Re: [RFC PATCH] block: Add new generic block device naming interface

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: <20130425204033.GB10990@mtj.dyndns.org>
Date:	Thu, 25 Apr 2013 13:40:33 -0700
From:	Tejun Heo <tj@...nel.org>
To:	"Stephen M. Cameron" <scameron@...rdog.cce.hp.com>
Cc:	axboe@...nel.dk, neilb@...e.de, hch@...radead.org,
	jmoyer@...hat.com, hare@...e.de, shaohua.li@...el.com,
	vgoyal@...hat.com, stephenmcameron@...il.com,
	linux-kernel@...r.kernel.org, lsorense@...lub.uwaterloo.ca
Subject: Re: [RFC PATCH] block: Add new generic block device naming interface

Hello,

On Thu, Apr 25, 2013 at 03:22:15PM -0500, Stephen M. Cameron wrote:
> If block drivers could (optionally) share a common device namespace then
> grub could be taught about this common namespace once, and any new block
> device drivers could take advantage of this namespace and grub would
> automatically work with them.

Hmmm... maybe I'm missing something but the names assigned this way
wouldn't have any kind of stability across boots.  Is that good
enough?  But, if so, I'm kinda having hard time understanding what
it'd be able to do which any other name can't do.

Can you please elaborate the use case?

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/