Received: by 10.223.164.221 with SMTP id h29csp33607wrb; Tue, 31 Oct 2017 09:35:55 -0700 (PDT) X-Google-Smtp-Source: ABhQp+Tb6rh+pmSEDkQWdqyRV/Vbl/HM2UEN30bz1RUH4DxU2eIpkuB/T2et1QxUveWo/CsiGLDZ X-Received: by 10.99.147.3 with SMTP id b3mr2405797pge.352.1509467755329; Tue, 31 Oct 2017 09:35:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1509467755; cv=none; d=google.com; s=arc-20160816; b=yeTuuEk8gtsaXE4aHRTR8OD3c0d6S8dcwp2yyvLJLnE/1h/PQc5ranTR6FC2ac7FbD uph1toXJogQV6wRn9jsOR0eC1jtmswPdQePfNLIPCI0Pm397JEBjuvxBrbMRRcAH6qS8 2wLKgGGWLsMzWoJdntcIwGka02EIBN+ZOTDYkBqTj+ntcvjV15Jf0PCsHSv8PiFuydkD 47AYfZ2pULKin+Jfd+MAU6MRW4fwlHgXf4za/IZ6x3hxg91c126ai2GqEXE2oB0o3EOa xZ14pKNMyxoiHwiWBeIqECjQ4V8+Rl51UvJedERl4Dxsvyjw/NzqOg+nP3xRv6ymCJ1r PsOg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dmarc-filter:arc-authentication-results; bh=WA0NHrKZ97BYFWWmbBgVuZJnb+JczNZntPsTB0O3u2A=; b=MhMHwrIzgOccyj6p4ugtfI3Ki4j9KRwsbgF9I7/ZmlNFf/mcABhxGG2R5pbZL9Lx6U sjUTAnQUtq2RfpetvhFMdFmsa4TzU8v+/Oy41n6bA3oklZbnzvDUmIDrcVTlSF7k3j73 LWR4aH1hLFQz/SJyF/r9BSHD8FpkpWmt48KlI02Gar0+2rnYKPg2KgyiBf33g4JpyR4G MnWcStN2E4HOxKUuaRu/vNs+T85vF2cM6qWFUaRHtMWj9IFKg0gIquYpccuLuE8jpNgI VjtTBT3WfS2f3Davydj6Yn0H0lG2rj55IQamWrWAomPv/BHiIYUjFGOsh0kSLlyMLiye m6Ug== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b1si1832132pgq.727.2017.10.31.09.35.41; Tue, 31 Oct 2017 09:35:55 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753634AbdJaQe6 (ORCPT + 99 others); Tue, 31 Oct 2017 12:34:58 -0400 Received: from mx1.redhat.com ([209.132.183.28]:57054 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751295AbdJaQe5 (ORCPT ); Tue, 31 Oct 2017 12:34:57 -0400 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id C0CF581138; Tue, 31 Oct 2017 16:34:55 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com C0CF581138 Authentication-Results: ext-mx03.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx03.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=oleg@redhat.com Received: from dhcp-27-174.brq.redhat.com (unknown [10.34.27.30]) by smtp.corp.redhat.com (Postfix) with SMTP id 08B88600CA; Tue, 31 Oct 2017 16:34:51 +0000 (UTC) Received: by dhcp-27-174.brq.redhat.com (nbSMTP-1.00) for uid 1000 oleg@redhat.com; Tue, 31 Oct 2017 17:34:55 +0100 (CET) Date: Tue, 31 Oct 2017 17:34:51 +0100 From: Oleg Nesterov To: Dmitry Vyukov Cc: syzbot , Andrew Morton , Arvind Yadav , Mark Brown , "Eric W. Biederman" , =?iso-8859-1?Q?Fr=E9d=E9ric?= Weisbecker , jamie.iles@oracle.com, LKML , "Martin K. Petersen" , mchehab@kernel.org, Ingo Molnar , mpe@ellerman.id.au, syzkaller-bugs@googlegroups.com, Al Viro Subject: Re: WARNING in task_participate_group_stop Message-ID: <20171031163451.GA30223@redhat.com> References: <94eb2c058c80ea49ed055cc8695e@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.27]); Tue, 31 Oct 2017 16:34:56 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/30, Dmitry Vyukov wrote: > > On Mon, Oct 30, 2017 at 10:12 PM, syzbot > > wrote: > > Hello, > > > > syzkaller hit the following crash on > > d95e159cd1da1ed4dbf76bf203e8ffaf231395e4 > > git://git.cmpxchg.org/linux-mmots.git/master > > compiler: gcc (GCC) 7.1.1 20170620 > > .config is attached > > Raw console output is attached. > > C reproducer is attached Hmm. I do not see reproducer in this email... > > syzkaller reproducer is attached. See https://goo.gl/kgGztJ > > for information about syzkaller reproducers > > This also happens on more recent commits, including linux-next > 36ef71cae353f88fd6e095e2aaa3e5953af1685d (Oct 19) and upstream > 3e0cc09a3a2c40ec1ffb6b4e12da86e98feccb11 (Oct 18). > > > WARNING: CPU: 0 PID: 1 at kernel/signal.c:340 > > task_participate_group_stop+0x1ce/0x230 kernel/signal.c:340 > > Kernel panic - not syncing: panic_on_warn set ... > > > > CPU: 0 PID: 1 Comm: init Not tainted 4.13.0-mm1+ #5 Looks familiar... I need some time to recall the details, will try to send the fix(es) this week. So this is init process with SIGNAL_UNKILLABLE flag set. And I hope it has the pending SIGKILL, otherwise there is something else. IIRC the problem is that complete_signal(SIGKILL) does nothing if SIGNAL_UNKILLABLE is set, in particular it doesn't set SIGNAL_GROUP_EXIT. This fools the signal_group_exit() check in do_signal_stop(). Actually there are more problems with SIGNAL_UNKILLABLE && SIGKILL, we need some nasty cleanups. Oleg. > > Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS > > Google 01/01/2011 > > Call Trace: > > __dump_stack lib/dump_stack.c:16 [inline] > > dump_stack+0x194/0x257 lib/dump_stack.c:52 > > panic+0x1e4/0x417 kernel/panic.c:181 > > __warn+0x1c4/0x1d9 kernel/panic.c:542 > > report_bug+0x211/0x2d0 lib/bug.c:183 > > fixup_bug+0x40/0x90 arch/x86/kernel/traps.c:178 > > do_trap_no_signal arch/x86/kernel/traps.c:212 [inline] > > do_trap+0x260/0x390 arch/x86/kernel/traps.c:261 > > do_error_trap+0x120/0x390 arch/x86/kernel/traps.c:298 > > do_invalid_op+0x1b/0x20 arch/x86/kernel/traps.c:311 > > invalid_op+0x18/0x20 arch/x86/entry/entry_64.S:905 > > RIP: 0010:task_participate_group_stop+0x1ce/0x230 kernel/signal.c:340 > > RSP: 0018:ffff8801d9ee77f0 EFLAGS: 00010097 > > RAX: ffff8801d9ed8040 RBX: ffff8801d9ed8040 RCX: ffff8801d9edb2c0 > > RDX: 0000000000000000 RSI: 0000000000060013 RDI: ffff8801d9ed84d0 > > RBP: ffff8801d9ee7808 R08: ffff8801d9ee7180 R09: ffff8801d9ee7178 > > R10: ffff8801d9ee70f0 R11: 1ffff1003b3db29b R12: ffff8801d9ee9740 > > R13: 0000000000000000 R14: dffffc0000000000 R15: ffff8801d9ed85c8 > > do_signal_stop+0x217/0x900 kernel/signal.c:2042 > > get_signal+0x61c/0x17e0 kernel/signal.c:2297 > > do_signal+0x94/0x1ee0 arch/x86/kernel/signal.c:808 > > exit_to_usermode_loop+0x224/0x300 arch/x86/entry/common.c:158 > > prepare_exit_to_usermode arch/x86/entry/common.c:197 [inline] > > syscall_return_slowpath+0x42f/0x500 arch/x86/entry/common.c:266 > > entry_SYSCALL_64_fastpath+0xbc/0xbe > > RIP: 0033:0x7f33f723fdd3 > > RSP: 002b:00007fffb5303398 EFLAGS: 00000246 ORIG_RAX: 0000000000000017 > > RAX: fffffffffffffdfe RBX: 00007fffb5303540 RCX: 00007f33f723fdd3 > > RDX: 0000000000000000 RSI: 00007fffb53036f0 RDI: 000000000000000b > > RBP: 00007fffb53036f0 R08: 00007fffb5303770 R09: 0000000000000001 > > R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff > > R13: 00007fffb5303ad0 R14: 0000000000000000 R15: 0000000000000000 > > > > > > --- > > This bug is generated by a dumb bot. It may contain errors. > > See https://goo.gl/tpsmEJ for details. > > Direct all questions to syzkaller@googlegroups.com. > > > > syzbot will keep track of this bug report. > > Once a fix for this bug is committed, please reply to this email with: > > #syz fix: exact-commit-title > > To mark this as a duplicate of another syzbot report, please reply with: > > #syz dup: exact-subject-of-another-report > > If it's a one-off invalid bug report, please reply with: > > #syz invalid > > Note: if the crash happens again, it will cause creation of a new bug > > report. > > > > -- > > You received this message because you are subscribed to the Google Groups > > "syzkaller-bugs" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to syzkaller-bugs+unsubscribe@googlegroups.com. > > To view this discussion on the web visit > > https://groups.google.com/d/msgid/syzkaller-bugs/94eb2c058c80ea49ed055cc8695e%40google.com. > > For more options, visit https://groups.google.com/d/optout. From 1582712110950747631@xxx Mon Oct 30 19:31:30 +0000 2017 X-GM-THRID: 1582711532474407023 X-Gmail-Labels: Inbox,Category Forums