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]

Message-Id: <20080925.130619.193699562.davem@davemloft.net>
Date:	Thu, 25 Sep 2008 13:06:19 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	jkosina@...e.cz
Cc:	elendil@...net.nl, airlied@...il.com, jeff@...zik.org,
	akpm@...ux-foundation.org, jeffrey.t.kirsher@...el.com,
	david.vrabel@....com, rjw@...k.pl, linux-kernel@...r.kernel.org,
	kernel-testers@...r.kernel.org, chrisl@...are.com, mingo@...e.hu,
	jbarnes@...tuousgeek.org, jesse.brandeburg@...il.com
Subject: Re: [Bug #11382] e1000e: 2.6.27-rc1 corrupts EEPROM/NVM

From: Jiri Kosina <jkosina@...e.cz>
Date: Thu, 25 Sep 2008 19:24:57 +0200 (CEST)

> If being set to 0 (it's so easy to call memset(0) on a bogus pointer, 
> there are usually lots of them in the code) or to random garbage, it would 
> seem to be much more understandable, than 0xff.

Setting framebuffer bytes to 0xff is pretty common, for example
for color keys and anti-aliasing pixel values.
--
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/