From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SPF_PASS,URIBL_BLOCKED,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7D87CC43381 for ; Sun, 24 Mar 2019 09:07:22 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 4278E2171F for ; Sun, 24 Mar 2019 09:07:22 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alien8.de header.i=@alien8.de header.b="OrxZhKTR" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728547AbfCXJHU (ORCPT ); Sun, 24 Mar 2019 05:07:20 -0400 Received: from mail.skyhub.de ([5.9.137.197]:56802 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726139AbfCXJHU (ORCPT ); Sun, 24 Mar 2019 05:07:20 -0400 Received: from zn.tnic (p200300EC2F098000329C23FFFEA6A903.dip0.t-ipconnect.de [IPv6:2003:ec:2f09:8000:329c:23ff:fea6:a903]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id E80B81EC0943; Sun, 24 Mar 2019 10:07:17 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1553418438; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:in-reply-to:in-reply-to: references:references; bh=5+KqYeiJDVJ/7D13VK14lDtUFrIBpzzYSO4qPPOt+iM=; b=OrxZhKTRmk3EyQlS31VWF8j+7sAmzo4AeFpMP6RMBrpOcSmxjh5uzfWXgGvm+DqN3AZ/9r fXqON7fi6fJ+9abWPjFk+41XMpBa2gFqey1JJlOz4UC1r97ubW+li4UkupX78+qXnk2cA3 UOR0TDIMO9jyvJQgzHuY1IVSAlKkZjY= Date: Sun, 24 Mar 2019 10:07:19 +0100 From: Borislav Petkov To: syzbot , syzkaller-bugs@googlegroups.com Cc: frederic@kernel.org, gustavo@embeddedor.com, hpa@zytor.com, linux-kernel@vger.kernel.org, mhiramat@kernel.org, mingo@redhat.com, syzkaller-bugs@googlegroups.com, tglx@linutronix.de, x86@kernel.org Subject: Re: WARNING in arch_install_hw_breakpoint Message-ID: <20190324090719.GA23289@zn.tnic> References: <000000000000639f6a0584d11b82@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <000000000000639f6a0584d11b82@google.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org syzbot folks, please fix your bot - I got 164(!) copies of this mail. No, wait, 165. This is really annoying. On Sat, Mar 23, 2019 at 11:22:06PM -0700, syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit: fd1f297b Merge tag 'drm-fixes-2019-03-22' of git://anongit.. > git tree: upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=1574f56d200000 > kernel config: https://syzkaller.appspot.com/x/.config?x=9a31fb246de2a622 > dashboard link: https://syzkaller.appspot.com/bug?extid=370a6b0f11867bf13515 > compiler: gcc (GCC) 9.0.0 20181231 (experimental) > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1157b7cf200000 > > Bisection is inconclusive: the bug happens on the oldest tested release. > > bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10ca39b3200000 > final crash: https://syzkaller.appspot.com/x/report.txt?x=12ca39b3200000 > console output: https://syzkaller.appspot.com/x/log.txt?x=14ca39b3200000 > > IMPORTANT: if you fix the bug, please add the following tag to the commit: > Reported-by: syzbot+370a6b0f11867bf13515@syzkaller.appspotmail.com > > ------------[ cut here ]------------ > Can't find any breakpoint slot > WARNING: CPU: 0 PID: 8058 at arch/x86/kernel/hw_breakpoint.c:121 > arch_install_hw_breakpoint+0x2d6/0x3a0 arch/x86/kernel/hw_breakpoint.c:121 > Kernel panic - not syncing: panic_on_warn set ... > CPU: 0 PID: 8058 Comm: syz-executor.1 Not tainted 5.1.0-rc1+ #33 > Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS > Google 01/01/2011 > Call Trace: > __dump_stack lib/dump_stack.c:77 [inline] > dump_stack+0x172/0x1f0 lib/dump_stack.c:113 > panic+0x2cb/0x65c kernel/panic.c:214 > __warn.cold+0x20/0x45 kernel/panic.c:571 > report_bug+0x263/0x2b0 lib/bug.c:186 > fixup_bug arch/x86/kernel/traps.c:179 [inline] > fixup_bug arch/x86/kernel/traps.c:174 [inline] > do_error_trap+0x11b/0x200 arch/x86/kernel/traps.c:272 > do_invalid_op+0x37/0x50 arch/x86/kernel/traps.c:291 > invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:973 > RIP: 0010:arch_install_hw_breakpoint+0x2d6/0x3a0 > arch/x86/kernel/hw_breakpoint.c:121 > Code: c8 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 0b 0f 0b 48 c7 c7 > 40 23 65 87 89 45 d4 c6 05 ed 9d 32 08 01 e8 98 43 1b 00 <0f> 0b 8b 45 d4 e9 > bc fd ff ff 40 88 75 c8 e8 a7 8e 80 00 0f b6 75 > RSP: 0018:ffff8880a512f6d8 EFLAGS: 00010086 > RAX: 0000000000000000 RBX: ffff8880ae81ec98 RCX: 0000000000000000 > RDX: 0000000040000000 RSI: ffffffff815ae266 RDI: ffffed1014a25ecd > RBP: ffff8880a512f718 R08: ffff8880857382c0 R09: fffffbfff11335f5 > R10: fffffbfff11335f4 R11: ffffffff8899afa3 R12: ffff888085730380 > R13: dffffc0000000000 R14: 0000000000000004 R15: 000000000001eca0 > hw_breakpoint_add+0xa7/0x130 kernel/events/hw_breakpoint.c:632 > event_sched_in kernel/events/core.c:2281 [inline] > event_sched_in.isra.0+0x373/0xbf0 kernel/events/core.c:2245 > group_sched_in+0xe4/0x3d0 kernel/events/core.c:2317 > flexible_sched_in+0x615/0x9c0 kernel/events/core.c:3311 > visit_groups_merge+0x336/0x5d0 kernel/events/core.c:3259 > ctx_flexible_sched_in kernel/events/core.c:3345 [inline] > ctx_sched_in+0x330/0x670 kernel/events/core.c:3390 > perf_event_sched_in+0x6e/0xa0 kernel/events/core.c:2426 > perf_event_context_sched_in kernel/events/core.c:3430 [inline] > __perf_event_task_sched_in+0x609/0x820 kernel/events/core.c:3469 > perf_event_task_sched_in include/linux/perf_event.h:1115 [inline] > finish_task_switch+0x2c2/0x780 kernel/sched/core.c:2725 > context_switch kernel/sched/core.c:2880 [inline] > __schedule+0x81f/0x1cc0 kernel/sched/core.c:3518 > schedule+0x92/0x180 kernel/sched/core.c:3562 > freezable_schedule include/linux/freezer.h:172 [inline] > ptrace_stop+0x3fe/0x950 kernel/signal.c:2111 > do_jobctl_trap kernel/signal.c:2330 [inline] > get_signal+0x1502/0x1d50 kernel/signal.c:2456 > do_signal+0x87/0x1940 arch/x86/kernel/signal.c:816 > exit_to_usermode_loop+0x244/0x2c0 arch/x86/entry/common.c:162 > prepare_exit_to_usermode arch/x86/entry/common.c:197 [inline] > syscall_return_slowpath arch/x86/entry/common.c:268 [inline] > do_syscall_64+0x52d/0x610 arch/x86/entry/common.c:293 > entry_SYSCALL_64_after_hwframe+0x49/0xbe > RIP: 0033:0x458209 > Code: ad b8 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7 > 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff > 0f 83 7b b8 fb ff c3 66 2e 0f 1f 84 00 00 00 00 > RSP: 002b:00007f6b1a2a8c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000129 > RAX: 0000000000000000 RBX: 0000000000000004 RCX: 0000000000458209 > RDX: 0000000000000016 RSI: 000000000000002a RDI: 000000000000002a > RBP: 000000000073bf00 R08: 0000000000000000 R09: 0000000000000000 > R10: 0000000020000100 R11: 0000000000000246 R12: 00007f6b1a2a96d4 > R13: 00000000004c4f84 R14: 00000000004d8bd8 R15: 00000000ffffffff > > ====================================================== > > > --- > This bug is generated by a bot. It may contain errors. > See https://goo.gl/tpsmEJ for more information about syzbot. > syzbot engineers can be reached at syzkaller@googlegroups.com. > > syzbot will keep track of this bug report. See: > https://goo.gl/tpsmEJ#status for how to communicate with syzbot. > For information about bisection process see: https://goo.gl/tpsmEJ#bisection > syzbot can test patches for this bug, for details see: > https://goo.gl/tpsmEJ#testing-patches -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.