| 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
| ||
|
Message-ID: <964414.64865.qm@web52908.mail.yahoo.com> Date: Wed, 24 Jan 2007 15:53:19 +0000 (GMT) From: Chris Rankin <rankincj@...oo.com> To: linux-kernel@...r.kernel.org Subject: Re: 2.6.18-stable release plans? > > But MY kernel is clearly untainted. > > So what other explanation is there apart from a kernel bug? > If it's me you're asking: I don't know (overheating, cosmic rays, ...) I suppose what I'm *really* asking is what the basis is for assuming that this *isn't* a kernel bug and can therefore be safely ignored, seeing as the oops is real, the hardware is fine and the kernel is untainted? That seems to cover the bases from where I'm sitting. Cheers, Chris P.S. No micro-heatwaves have occurred here, either. Do we all need to install muon detectors in our homes before reporting bugs now, so that we can exclude cosmic ray events too? ___________________________________________________________ To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com - 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/
Powered by blists - more mailing lists