Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1280106
| From | Peter Zijlstra <peterz@infradead.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: WARNING: CPU: 12 PID: 16862 at ./arch/x86/include/asm/thread_info.h:236 |
| Date | 2015-11-30 18:00 +0100 |
| Message-ID | <qAzXY-69w-11@gated-at.bofh.it> (permalink) |
| References | <qAzuW-5YC-27@gated-at.bofh.it> <qAzOi-66r-25@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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/
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
WARNING: CPU: 12 PID: 16862 at ./arch/x86/include/asm/thread_info.h:236 Sasha Levin <sasha.levin@oracle.com> - 2015-11-30 17:30 +0100
Re: WARNING: CPU: 12 PID: 16862 at ./arch/x86/include/asm/thread_info.h:236 Al Viro <viro@ZenIV.linux.org.uk> - 2015-11-30 17:50 +0100
Re: WARNING: CPU: 12 PID: 16862 at ./arch/x86/include/asm/thread_info.h:236 Peter Zijlstra <peterz@infradead.org> - 2015-11-30 18:00 +0100
Re: WARNING: CPU: 12 PID: 16862 at ./arch/x86/include/asm/thread_info.h:236 Oleg Nesterov <oleg@redhat.com> - 2015-11-30 19:50 +0100
csiph-web