| 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
| ||
|
Date: Tue, 29 Dec 2009 22:32:31 +0000 From: Luís Picciochi Oliveira <pitxyoki@...il.com> To: "Rafael J. Wysocki" <rjw@...k.pl> Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Kernel Testers List <kernel-testers@...r.kernel.org> Subject: Re: [Bug #14436] Computer becomes unusable without any apparent reason On Tue, Dec 29, 2009 at 10:04 PM, Rafael J. Wysocki <rjw@...k.pl> wrote: > On Tuesday 29 December 2009, Luís Picciochi Oliveira wrote: >> Hi, >> The bug is present on 2.6.32 and subsequent versions (2.6.32.1, 2.6.32.2). >> It has been resolved as of 2.6.33-rc1. > > Thanks for the update. > > Is it known how it was fixed in 2.6.33-rc1 or do you just see that the bug is > not present in there any more? Hi, Like I reported at [1], I strongly believe this was the same as bug as #12794, which was resolved by a patch resulting from my feedback and Jussi Kivilinna's work. After I enabled memory debug like suggested on bug #14436, everything pointed in the direction of that bug. The issue was solved after applying Jussi's patch. That patch has been commited to the mainline kernel and I can assert that since then the bug didn't occur again. Regards, Luís Picciochi [1] http://bugzilla.kernel.org/show_bug.cgi?id=14436 -- 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