linux-kernel - Re: WARNING: CPU: 12 PID: 16862 at ./arch/x86/include/asm/thread

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]

Message-ID: <20151130165244.GA3816@twins.programming.kicks-ass.net>
Date:	Mon, 30 Nov 2015 17:52:44 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Al Viro <viro@...IV.linux.org.uk>
Cc:	Sasha Levin <sasha.levin@...cle.com>,
	Ingo Molnar <mingo@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Oleg Nesterov <oleg@...hat.com>
Subject: Re: WARNING: CPU: 12 PID: 16862 at
 ./arch/x86/include/asm/thread_info.h:236

On Mon, Nov 30, 2015 at 04:44:05PM +0000, Al Viro wrote:
> On Mon, Nov 30, 2015 at 11:20:44AM -0500, Sasha Levin wrote:
> > Hi all,
> > 
> > I've hit the following while fuzzing with trinity on the latest -next kernel:
> 
>         __set_current_state(TASK_INTERRUPTIBLE);
>         schedule();
>         set_restore_sigmask();
> 
> somehow got out of schedule() without TIF_SIGPENDING being set...

A random wakeup (which are always possible) can make that happen, right?

I'm (as always) a little vague on signals, but who is responsible for
setting that bit?
--
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/