Re: Oops with tip/x86/fpu

From: Quentin Casasnovas
Date: Fri Mar 27 2015 - 03:28:43 EST


On Thu, Mar 26, 2015 at 10:48:18PM +0000, Yu, Fenghua wrote:
> > > sctxt->fpstate=(void *)1 changes the fpstate pointer in the
> > > sigcontext. It will generate segfault and bad frame info in kernel.
> > >
> > > This is expected behavior, right? Is this still a valid test?
> >
> > Just to be clear, I saw a full-on kernel panic induced from an unprivileged
> > application.
> >
> > Are you seeing something different?
>
> I use latest tip tree. Maybe it has the fixes already. I see "bad frame"
> reported in kernel. Seems the issue has been fixed in tip tree.
>

Fenghua, if you're interested, the details are now public here:

http://seclists.org/oss-sec/2015/q1/877

Quentin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/