Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752861AbbK3Qws (ORCPT ); Mon, 30 Nov 2015 11:52:48 -0500 Received: from casper.infradead.org ([85.118.1.10]:55929 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751847AbbK3Qwr (ORCPT ); Mon, 30 Nov 2015 11:52:47 -0500 Date: Mon, 30 Nov 2015 17:52:44 +0100 From: Peter Zijlstra To: Al Viro Cc: Sasha Levin , Ingo Molnar , LKML , Oleg Nesterov Subject: Re: WARNING: CPU: 12 PID: 16862 at ./arch/x86/include/asm/thread_info.h:236 Message-ID: <20151130165244.GA3816@twins.programming.kicks-ass.net> References: <565C775C.9050004@oracle.com> <20151130164404.GZ22011@ZenIV.linux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151130164404.GZ22011@ZenIV.linux.org.uk> User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 807 Lines: 21 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/