linux-kernel - Re: [tip:x86/asm] x86/entry/32: Switch INT80 to the new C syscall path

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-next>] [day] [month] [year] [list]

Message-ID: <CALCETrV4cT77Hv-Um2KqygN8RQYFb_E=P4czt=WD5XcvFLCTvg@mail.gmail.com>
Date:	Fri, 16 Oct 2015 08:57:09 -0700
From:	Andy Lutomirski <luto@...capital.net>
To:	Borislav Petkov <bp@...en8.de>
Cc:	"linux-tip-commits@...r.kernel.org" 
	<linux-tip-commits@...r.kernel.org>,
	"H. Peter Anvin" <hpa@...or.com>,
	Andrew Lutomirski <luto@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Brian Gerst <brgerst@...il.com>,
	Ingo Molnar <mingo@...nel.org>,
	Denys Vlasenko <dvlasenk@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [tip:x86/asm] x86/entry/32: Switch INT80 to the new C syscall path

On Fri, Oct 16, 2015 at 7:05 AM, Borislav Petkov <bp@...en8.de> wrote:
>
> On Fri, Oct 16, 2015 at 12:52:29PM +0200, Borislav Petkov wrote:
> > > > Just triggered this here on rc5+tip/master, 32-bit. Any ideas?
> > > >
> > > > ------------[ cut here ]------------
> > > > WARNING: CPU: 1 PID: 1 at /mnt/kernel/kernel/linux-2.6/kernel/locking/lockdep.c:2639 trace_hardirqs_off_caller+0xef/0x150()
> > > > DEBUG_LOCKS_WARN_ON(!irqs_disabled())
> > > > Modules linked in:
>
> Hmm, something more is b0rked with this. I'm attaching a #GP splat from
> the intel laptop. Yeah, the box has paniced and the only way to catch it
> is a photo (how convenient that cameras are ubiquitous nowadays...).
>
> I see prepare_exit_to_usermode and do_signal ...
>
> Fun stuff :-\


Is this AMD or Intel?  If it's Intel, can you see if booting with
nosep fixes it?

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