From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1753337AbcA2ONy (ORCPT <rfc822;w@1wt.eu>);
	Fri, 29 Jan 2016 09:13:54 -0500
Received: from mx1.redhat.com ([209.132.183.28]:58029 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751141AbcA2ONx (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Fri, 29 Jan 2016 09:13:53 -0500
Date: Fri, 29 Jan 2016 15:13:47 +0100
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
Message-ID: <20160129141347.GA22082@redhat.com>
References: <CACT4Y+a+O5MXtZd5U-3t_7vQFhGaRCwMhrTB5OCcN5s=i4sTJg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CACT4Y+a+O5MXtZd5U-3t_7vQFhGaRCwMhrTB5OCcN5s=i4sTJg@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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.