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: <20130429151719.GG8204@redhat.com>
Date:	Mon, 29 Apr 2013 11:17:19 -0400
From:	Vivek Goyal <vgoyal@...hat.com>
To:	Hannes Reinecke <hare@...e.de>
Cc:	Tejun Heo <tj@...nel.org>, scameron@...rdog.cce.hp.com,
	axboe@...nel.dk, neilb@...e.de, hch@...radead.org,
	jmoyer@...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

On Mon, Apr 29, 2013 at 04:56:38PM +0200, Hannes Reinecke wrote:
> On 04/26/2013 09:03 PM, Tejun Heo wrote:
> > hey,
> > 
> > On Thu, Apr 25, 2013 at 05:12:20PM -0500, scameron@...rdog.cce.hp.com wrote:
> >> It looks like these are called from a function called init_device_map() 
> >> that is called from grub_stage2() at least in the version of grub I looked
> >> at (0.97, from rhel6).
> >>
> >> So my assumption is that adding a new block driver with yet another name space
> >> would require adding another bit of code into grub like those above.  When I
> >> asked about "best practices" for new block driver device names on the grub devel
> >> mailing list to minimize required changes to grub, nobody argued against that
> >> assumption. 
> > 
> > I think we kinda need to get down to the root cause of the issue.
> > Nothing against giving common names to devices in itself but there's a
> > non-insigificant chance that we end up with something half-way if the
> > original problem isn't properly understodd.
> > 
> Oh, the problem _is_ well understood.
> 
> It's the design of grub :-)
> 
> grub requires you to re-implement _every_ device naming scheme which
> is present in the kernel.

So then grub needs to be fixed and not the other way around?

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