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] [day] [month] [year] [list]

Date:	Mon, 29 Apr 2013 09:06:04 -0700
From:	Tejun Heo <tj@...nel.org>
To:	Hannes Reinecke <hare@...e.de>
Cc:	scameron@...rdog.cce.hp.com, axboe@...nel.dk, neilb@...e.de,
	hch@...radead.org, jmoyer@...hat.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

Hey,

On Mon, Apr 29, 2013 at 04:56:38PM +0200, Hannes Reinecke wrote:
> grub requires you to re-implement _every_ device naming scheme which
> is present in the kernel.

Are you saying that it's just a limitation in grub?

> And no, you cannot use the kernel itself as grub is run _prior_ to
> the kernel.

I don't get this part.  While booting, it's all about the number BIOS
assigned to disks.  After boot, we might as well just do mknod
/dev/grub-device-N if grub is picky about the names it accept.  What
am I missing here?

> As there is no common naming scheme for block devices each and
> every block device driver has implemented it own.
> So grub need to re-implement each and every device naming
> for these drivers.

Sure, I heard that a couple times but nobody really explained why
that's the case.  Is it something fundamental or is it just an
implementation artifact?  Can't it be fixed from grub side?  If not,
why?

> The approach from Stephen would solve that.

At the cost of losing per-driver semi-stable enumeration.  I don't
think we want to lose that in favor of working around an
implementation detail in grub.

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/