Re: WARNING in set_restore_sigmask

2016-02-01 Thread Andrew Morton
On Fri, 29 Jan 2016 15:13:47 +0100 Oleg Nesterov wrote: > On 01/29, Dmitry Vyukov wrote: > > > > Hello, > > > > I've got the following WARNING while running syzkaller fuzzer: > > > > [ cut here ] > > WARNING: CPU: 2 PID: 10905 at ./arch/x86/include/asm/thread_info.h:236 >

Re: WARNING in set_restore_sigmask

2016-01-29 Thread Steven Rostedt
On Fri, 29 Jan 2016 15:10:18 +0100 (CET) Thomas Gleixner wrote: > The time depends on the serial speed and the trace buffer size and the number > of cpus. Don't worry about the uptime. The buffer is a ringbuffer with limited > capacity, so the dump time is constant. > > If you want that /proc/s

Re: WARNING in set_restore_sigmask

2016-01-29 Thread Thomas Gleixner
On Fri, 29 Jan 2016, Oleg Nesterov wrote: > > [] sigsuspend+0x18e/0x1f0 kernel/signal.c:3513 > > See http://marc.info/?t=14537372204 the patch is already in -mm tree. Nice! So my analysis was not that far off. Thanks, tglx

Re: WARNING in set_restore_sigmask

2016-01-29 Thread Oleg Nesterov
On 01/29, Dmitry Vyukov wrote: > > Hello, > > I've got the following WARNING while running syzkaller fuzzer: > > [ cut here ] > WARNING: CPU: 2 PID: 10905 at ./arch/x86/include/asm/thread_info.h:236 > sigsuspend+0x18e/0x1f0() > Modules linked in: > CPU: 2 PID: 10905 Comm: sy

Re: WARNING in set_restore_sigmask

2016-01-29 Thread Thomas Gleixner
On Fri, 29 Jan 2016, Dmitry Vyukov wrote: > On Fri, Jan 29, 2016 at 2:57 PM, Thomas Gleixner wrote: > I need something that will work without supervision. I need to use > /proc/sys/kernel/ftrace_dump_on_oops instead of > /proc/sys/kernel/traceoff_on_warning then, right? > > Quite some time? Does

Re: WARNING in set_restore_sigmask

2016-01-29 Thread Dmitry Vyukov
On Fri, Jan 29, 2016 at 2:57 PM, Thomas Gleixner wrote: > On Fri, 29 Jan 2016, Dmitry Vyukov wrote: >> On Fri, Jan 29, 2016 at 12:53 PM, Thomas Gleixner wrote: >> > Dmitry, >> > >> > On Fri, 29 Jan 2016, Dmitry Vyukov wrote: >> >> WARNING: CPU: 2 PID: 10905 at ./arch/x86/include/asm/thread_info.h

Re: WARNING in set_restore_sigmask

2016-01-29 Thread Thomas Gleixner
On Fri, 29 Jan 2016, Dmitry Vyukov wrote: > On Fri, Jan 29, 2016 at 12:53 PM, Thomas Gleixner wrote: > > Dmitry, > > > > On Fri, 29 Jan 2016, Dmitry Vyukov wrote: > >> WARNING: CPU: 2 PID: 10905 at ./arch/x86/include/asm/thread_info.h:236 > >> sigsuspend+0x18e/0x1f0() > >> Modules linked in: > >>

Re: WARNING in set_restore_sigmask

2016-01-29 Thread Dmitry Vyukov
On Fri, Jan 29, 2016 at 12:53 PM, Thomas Gleixner wrote: > Dmitry, > > On Fri, 29 Jan 2016, Dmitry Vyukov wrote: >> WARNING: CPU: 2 PID: 10905 at ./arch/x86/include/asm/thread_info.h:236 >> sigsuspend+0x18e/0x1f0() >> Modules linked in: >> CPU: 2 PID: 10905 Comm: syz-executor Not tainted 4.5.0-rc1

Re: WARNING in set_restore_sigmask

2016-01-29 Thread Thomas Gleixner
Dmitry, On Fri, 29 Jan 2016, Dmitry Vyukov wrote: > WARNING: CPU: 2 PID: 10905 at ./arch/x86/include/asm/thread_info.h:236 > sigsuspend+0x18e/0x1f0() > Modules linked in: > CPU: 2 PID: 10905 Comm: syz-executor Not tainted 4.5.0-rc1+ #300 > Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIO

Re: WARNING in set_restore_sigmask

2016-01-29 Thread Dmitry Vyukov
On Fri, Jan 29, 2016 at 10:16 AM, Dmitry Vyukov wrote: > Hello, > > I've got the following WARNING while running syzkaller fuzzer: > > [ cut here ] > WARNING: CPU: 2 PID: 10905 at ./arch/x86/include/asm/thread_info.h:236 > sigsuspend+0x18e/0x1f0() > Modules linked in: > CPU