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]
Date:	Tue, 14 Dec 2010 13:54:45 -0600
From:	Matt Domsch <Matt_Domsch@...l.com>
To:	Narendra_K@...l.com
Cc:	linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org,
	Jordan_Hargrave@...l.com, Charles_Rose@...l.com
Subject: Re: [PATCH] Enable pci=bfsort by default on future Dell systems

On Tue, Dec 14, 2010 at 09:57:12AM -0800, Narendra_K@...l.com wrote:
> Hello,
> 
> This patch enables pci=bfsort by default on future Dell systems.
> Please consider for inclusion if acceptable.
> 
> From: Jordan Hargrave <jordan_hargrave@...l.com>
> Subject: [PATCH] Enable pci=bfsort by default on future Dell systems

You may be asking "why is this necessary with the biosdevname work
going on?".  Short story is, yes, biosdevname continues to be the
medium-term strategy, and we are addressing as much as we can in that,
getting into all the distributions future releases, adding it in the
distro installer environments.  However, biosdevname adoption has been
slow (I started writing it 5 years ago), and there's a good chance it
won't be picked up by all older distribution releases in Service
Packs, Updates, or the like.  By continuing to use the pci=bfsort
workaround, we can more likely get this small patch into older
distribution update relesaes where we are already doing hardware
enablement, as it can only affect future Dell servers, no impact to
existing systems or installations.  It also gives flexibility to
current kernels and distribution releases on when they pick up
biosdevname.  The two (pci=bfsort and biosdevname) do not conflict in
any way.

So, I encourage adoption of this small kernel patch, and then
encourage distros to pick up biosdevname also.

Thanks,
Matt

-- 
Matt Domsch
Technology Strategist
Dell | Office of the CTO
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ