linux-kernel - Re: 2.6.18-stable release plans?

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, 01 Feb 2007 23:02:07 -0500
From:	Valdis.Kletnieks@...edu
To:	Chris Rankin <rankincj@...oo.com>
Cc:	Mark Rustad <mrustad@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: 2.6.18-stable release plans?

On Wed, 24 Jan 2007 22:37:20 GMT, Chris Rankin said:
> --- Mark Rustad <mrustad@...il.com> wrote:
> > Well, do you have ECC memory? If not, it is at least possible that  
> > that the solar flares that occurred last month may have affected your  
> > system.
> 
> I am going to assume that you are being facaetious, because it would be the rarified pinnacle of
> supreme arrogance to suggest that a cosmic ray event is a more likely explanation than a bug in
> the kernel.

Sorry for the late reply, but cosmic ray events (actually, self-induced alpha
particle events from decays within the chipset itself) *are* a likely
explanation:

http://stason.org/TULARC/pc/pc_hardware_faq/2_20_What_does_parity_ECC_memory_protect_the_system_from.html

Most important take-away here:

"With 100 million computers in use today, we should expect roughly 6 million
single bit errors per year. Computer hardware and software companies must
receive thousands of "side effect" bug reports and support calls due to memory
errors alone. The costs of NOT including parity memory must be huge!"

Content of type "application/pgp-signature" skipped