linux-kernel - Re: [PATCH] x86/mrst: add SFI platform device parsing code

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:	Thu, 23 Sep 2010 15:46:07 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Alan Cox <alan@...ux.intel.com>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Grant Likely <grant.likely@...retlab.ca>,
	linux-kernel@...r.kernel.org, x86@...nel.org,
	David Woodhouse <dwmw2@...radead.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] x86/mrst: add SFI platform device parsing code

On Thu, Sep 23, 2010 at 02:27:20PM +0100, Alan Cox wrote:

> > What is it about this platform that is going to restrict the problem?

> The sort of people who will be using it and how,

Can you be more specific?  This is the same sort of thing people
normally say but the experience is that it rarely survives a successful
product.

> > Code which makes this sort of assumption about knowing the platforms
> > that the device will be deployed on well is relatively common but the
> > usual result is that OEMs want to change the reference platforms and
> > the assumptions that the code has been making about the systems and
> > about how people will work with the code break down.

> There are non reference platforms in existence without the problem you
> envisage having occurred. So I think we'll worry about it if it happens
> but knowing that with DMI we have the tools to deal with this.

It doesn't break down immediately; a combination of volume and the next
generation product coming along and grabbing attention is usually what
causes things to break down.  However, if you're totally confident that
all the BIOS authors at the OEMs are going to work well together here
then I guess it's only Moorestown that's affected.
--
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/