linux-kernel - Re: [Bug #11382] e1000e: 2.6.27-rc1 corrupts EEPROM/NVM

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:	Fri, 26 Sep 2008 07:06:23 +1000
From:	"Dave Airlie" <airlied@...il.com>
To:	"Jiri Kosina" <jkosina@...e.cz>
Cc:	"Jesse Barnes" <jbarnes@...tuousgeek.org>,
	"Frans Pop" <elendil@...net.nl>, "Jeff Garzik" <jeff@...zik.org>,
	davem@...emloft.net, jeffrey.t.kirsher@...el.com,
	david.vrabel@....com, rjw@...k.pl, linux-kernel@...r.kernel.org,
	kernel-testers@...r.kernel.org, chrisl@...are.com,
	"Ingo Molnar" <mingo@...e.hu>, jesse.brandeburg@...il.com
Subject: Re: [Bug #11382] e1000e: 2.6.27-rc1 corrupts EEPROM/NVM

On Fri, Sep 26, 2008 at 6:35 AM, Jiri Kosina <jkosina@...e.cz> wrote:
> On Thu, 25 Sep 2008, Jesse Barnes wrote:
>
>> However, the "Factory" log at #425480 *does* indicate that a GEM aware
>> 2D driver was loaded (the "[drm:i915_getparam] *ERROR* Unknown parameter
>> 5" message indicates as much), but the kernel was definitely not GEM
>> aware otherwise the call would have succeeded.  So that rules out GEM
>> proper, but it could still be a bug in one of the non-GEM paths in the
>> experimental xf86-video-intel bits the various distros seem to be
>> picking up.
>
> That was exactly the point I was trying to make, that these error paths
> will probably also need auditing, once we rule out the possibility of
> NVRAM being overwritten from kernelspace.
>

Well the non-GEM paths are really the old codepaths we used in the
older drivers..

So unless we do something really dumb...

I'd target three areas PAT, pciaccess and e1000e itself.

Dave.
--
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/