From: Oleg Nesterov <oleg@redhat.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Richard Weinberger <richard@nod.at>,
"Amanieu d'Antras" <amanieu@gmail.com>,
Chris Metcalf <cmetcalf@ezchip.com>,
Andy Lutomirski <luto@amacapital.net>,
Davidlohr Bueso <dave@stgolabs.net>,
Vladimir Davydov <vdavydov@parallels.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: WARNING in set_restore_sigmask
Date: Fri, 29 Jan 2016 15:13:47 +0100 [thread overview]
Message-ID: <20160129141347.GA22082@redhat.com> (raw)
In-Reply-To: <CACT4Y+a+O5MXtZd5U-3t_7vQFhGaRCwMhrTB5OCcN5s=i4sTJg@mail.gmail.com>
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: syz-executor Not tainted 4.5.0-rc1+ #300
> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011
> 00000000ffffffff ffff88006139fe38 ffffffff82be118d 0000000000000000
> ffff88006d054740 ffffffff867387e0 ffff88006139fe78 ffffffff813536d9
> ffffffff813839ce ffffffff867387e0 00000000000000ec 0000000020000000
> Call Trace:
> [< inline >] __dump_stack lib/dump_stack.c:15
> [<ffffffff82be118d>] dump_stack+0x6f/0xa2 lib/dump_stack.c:50
> [<ffffffff813536d9>] warn_slowpath_common+0xd9/0x140 kernel/panic.c:482
> [<ffffffff81353909>] warn_slowpath_null+0x29/0x30 kernel/panic.c:515
> [< inline >] set_restore_sigmask
> ./arch/x86/include/asm/thread_info.h:236
> [<ffffffff813839ce>] sigsuspend+0x18e/0x1f0 kernel/signal.c:3513
See http://marc.info/?t=145373722000004 the patch is already in -mm tree.
Oleg.
next prev parent reply other threads:[~2016-01-29 14:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 9:16 WARNING in set_restore_sigmask Dmitry Vyukov
2016-01-29 9:24 ` Dmitry Vyukov
2016-01-29 11:53 ` Thomas Gleixner
2016-01-29 13:16 ` Dmitry Vyukov
2016-01-29 13:57 ` Thomas Gleixner
2016-01-29 14:05 ` Dmitry Vyukov
2016-01-29 14:10 ` Thomas Gleixner
2016-01-29 14:32 ` Steven Rostedt
2016-01-29 14:13 ` Oleg Nesterov [this message]
2016-01-29 14:16 ` Thomas Gleixner
2016-02-01 22:46 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160129141347.GA22082@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=amanieu@gmail.com \
--cc=cmetcalf@ezchip.com \
--cc=dave@stgolabs.net \
--cc=dvyukov@google.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=palmer@dabbelt.com \
--cc=richard@nod.at \
--cc=tglx@linutronix.de \
--cc=vdavydov@parallels.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.