| 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: <Pine.LNX.4.64.0701241607160.17843@blonde.wat.veritas.com> Date: Wed, 24 Jan 2007 16:12:46 +0000 (GMT) From: Hugh Dickins <hugh@...itas.com> To: Chris Rankin <rankincj@...oo.com> cc: linux-kernel@...r.kernel.org Subject: Re: 2.6.18-stable release plans? On Wed, 24 Jan 2007, Chris Rankin wrote: > > 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. All I'm claiming is that it's no more a reason to avoid 2.6.19* than to avoid any other release (the kernels before 2.6.7 happened to have no such check, but that doesn't imply they were any safer). It may indeed be due to a kernel bug, but I can't tell you where: sorry. Hugh - 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