linux-kernel - Re: Oops with strace

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 7 May 2008 19:26:20 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Eric Sesterhenn <snakebyte@....de>
cc:	Ingo Molnar <mingo@...e.hu>, Frederik Deweerdt <deweerdt@...e.fr>,
	linux-kernel@...r.kernel.org, suresh.b.siddha@...el.com,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: Oops with strace_test

On Wed, 7 May 2008, Eric Sesterhenn wrote:
> * Thomas Gleixner (tglx@...utronix.de) wrote:
> > On Wed, 7 May 2008, Eric Sesterhenn wrote:
> > > * Ingo Molnar (mingo@...e.hu) wrote:
> > > > 
> > > > * Frederik Deweerdt <deweerdt@...e.fr> wrote:
> > > > 
> > > > > Hi Eric,
> > > > > 
> > > > > This appears to be caused by init_fpu() missing from the 
> > > > > restore_sigcontext->restore_i387->restore_fpu_checking code path.
> > > > > 
> > > > > I believe that moving the init_fpu() call from math_state_restore to 
> > > > > restore_fpu_checking should fix the problem?
> > > 
> > > sadly the patch does not work for me :( I still get the oopses. I am
> > > running this on a 32 Bit CPU, so arch/x86/kernel/traps_64.c doesnt get
> > > compiled. I tried removing the same part from traps_32.c but then
> > > the kernel oopses before netconsole is active.
> > 
> > I run that &$#@! intuitive test for an hour know with no effect. Can
> > you please provide your .config file ?
> 
> sorry, ignored the CC, here it is.

Ok, we decoded the problem in meantime. Suresh will send a patch soon.

Thanks,

	tglx
--
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/