linux-kernel - Re: [PATCH] Enable pci=bfsort by default on future Dell systems

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:12:43 -0700
From:	Matthew Wilcox <matthew@....cx>
To:	Matt Domsch <Matt_Domsch@...l.com>
Cc:	Narendra_K@...l.com, 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 01:54:45PM -0600, Matt Domsch wrote:
> 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.

Actually, how about we introduce a smaller patch that just makes
bfsort the default for all machines with a BIOS date of 2011 or later?
bfsort was what we always intended; it was unintentionally broken for,
what, five years, and the only reason not to revert it was to not break
setups that had come to rely on it.

So just make it the default for all future systems, no matter what
manufacturer.

-- 
Matthew Wilcox				Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."
--
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/