Re: A commit between 2.6.16.4 and 2.6.16.5 failed crashme

2006-11-29 Thread Zhao Forrest
Thanks for your report. A git-bisect might be a bit of overkill considering that there were only two patches applied beween 2.6.16.4 and 2.6.16.5: Andi Kleen (2): x86_64: Clean up execve x86_64: When user could have changed RIP always force IRET (CVE-2006-0744) I've attached both p

Re: A commit between 2.6.16.4 and 2.6.16.5 failed crashme

2006-11-29 Thread Zhao Forrest
On 11/29/06, Adrian Bunk <[EMAIL PROTECTED]> wrote: On Wed, Nov 29, 2006 at 12:18:18AM -0800, Zhao Forrest wrote: > On 11/28/06, Andi Kleen <[EMAIL PROTECTED]> 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 call

Re: A commit between 2.6.16.4 and 2.6.16.5 failed crashme

2006-11-29 Thread Adrian Bunk
On Wed, Nov 29, 2006 at 12:18:18AM -0800, Zhao Forrest wrote: > On 11/28/06, Andi Kleen <[EMAIL PROTECTED]> 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

Re: A commit between 2.6.16.4 and 2.6.16.5 failed crashme

2006-11-29 Thread Zhao Forrest
On 11/28/06, Andi Kleen <[EMAIL PROTECTED]> 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