| 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
| ||
|
Date: Fri, 26 Apr 2013 12:03:33 -0700 From: Tejun Heo <tj@...nel.org> To: scameron@...rdog.cce.hp.com Cc: axboe@...nel.dk, neilb@...e.de, hch@...radead.org, jmoyer@...hat.com, hare@...e.de, 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 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. 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/
Powered by blists - more mailing lists