| 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: <ac8af0be0611290018y70c68a66r5a3199f08e6417d5@mail.gmail.com> Date: Wed, 29 Nov 2006 00:18:18 -0800 From: "Zhao Forrest" <forrest.zhao@...il.com> To: "Andi Kleen" <ak@...e.de>, bunk@...sta.de Cc: discuss@...-64.org, linux-kernel@...r.kernel.org Subject: Re: A commit between 2.6.16.4 and 2.6.16.5 failed crashme On 11/28/06, Andi Kleen <ak@...e.de> wrote: > > > I first need to contact the author of test case if we could send the > > test case to open source. The test case is called "crashme", > > Is that the classical crashme as found in LTP or an enhanced one? > Do you run it in a special way? Is the crash reproducible? > > We normally run crashme regularly as part of LTP, Cerberus etc. > so at least any obvious bugs should in theory be caught. > Let me change the subject of this thread. I just read our private version of crashme. It's based on crashme version 2.4 and add some logging capability, no other enhancement. So it should be the same as crashme in LTP. It is solidly reproducible within 3 minutes of running crashme. The current status is: we know it's a commit between 2.6.16.4 and 2.6.16.5 that introduce this bug. Our network is very slow(only 5-6K/second). So we'll start the git-bisect tomorrow after finishing downloading the 2.6.16 stable git tree. Thanks, Forrest - 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