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=-12.6 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 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 02632C433F5 for ; Mon, 6 Sep 2021 18:53:38 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id D93256103E for ; Mon, 6 Sep 2021 18:53:37 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S244395AbhIFSyl (ORCPT ); Mon, 6 Sep 2021 14:54:41 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36226 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233083AbhIFSyf (ORCPT ); Mon, 6 Sep 2021 14:54:35 -0400 Received: from mail-oi1-x234.google.com (mail-oi1-x234.google.com [IPv6:2607:f8b0:4864:20::234]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 57F89C061575 for ; Mon, 6 Sep 2021 11:53:30 -0700 (PDT) Received: by mail-oi1-x234.google.com with SMTP id s20so9840784oiw.3 for ; Mon, 06 Sep 2021 11:53:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=sender:to:cc:references:from:subject:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=UcnLLOWTICGf6PugP2nZxYm94B1HTwM9kfSyf808wwY=; b=K1/glI5P1Zai0NuuYuwZt4jNm/ZRfHu6rlGUkalNlL3LnlUiDmqJGW+C9dG2X//AS7 7o7cDEaw6uT06EFoagW0f5IRsi/n8szA+MGp8d8yieVQ578Q/vWSRUGrmecCRtNneaFK L7VSrJ5MsxZFCC2oyGOMSjdF5evsGZT5DpZCb2AGNk3prVkSoLaBuezthI9Zn9498WRi Ygfko6K6OqkewhCU+Wluwr0XI1n/TIlUWIoED7y5hA5nOW6LD2jsAUMdHplHF5jQNN9Q sTKFZ+zyD5dTMrjV4KbQ8xzY3iDjzRwoL2xxeUGEyexBtLzSw2QoUsbXnStaQeehOpKA 2jrA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:to:cc:references:from:subject:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=UcnLLOWTICGf6PugP2nZxYm94B1HTwM9kfSyf808wwY=; b=BXN3jfVdzypxIn2EIkrwjTzlIyuGFWrbEIXO99VFNQwd57mwuUBN1sMi9oWJ4miX0/ aWOzaUU/E70pWg1GCS7YUGl1F95IALEvcr5O3qGoT0MYBlIRII0x6xtYD53i0ZiQe/AI UwGzOolJDKCrJ8iGsfl2ge3PukGCGYnZGtawc7pOafuu1fGP9fDlZT5kAnMNfG398ZaZ u+91aNd1zu7jUNO8lO4nqS4CBOnJxpKi2Wi66yrcKOPPcRmNAt+JwfEwMRZr1o37mboG jQNr8YakulOSe8UdY5VKisalYU8s53mwmhwSYPtLSkWOEAm3OVy6FwguoeUGZbU7Ypy9 1YRw== X-Gm-Message-State: AOAM530CiMMTIW17XOjGs2STLuzNhSZQJhigZHpmDlyTqPN/ix5bSW21 xOeOZbaF2JqR9hq63ipItcLjObMgXg0= X-Google-Smtp-Source: ABdhPJxHBtMcCaSxJIn5JIBPRYFs9K6iemHD5M7I/AZwul44GNeuNqBpp8YZ07eTfPFyhFa29y9D5g== X-Received: by 2002:a05:6808:21a3:: with SMTP id be35mr382304oib.31.1630954409601; Mon, 06 Sep 2021 11:53:29 -0700 (PDT) Received: from server.roeck-us.net ([2600:1700:e321:62f0:329c:23ff:fee3:9d7c]) by smtp.gmail.com with ESMTPSA id a4sm1940106otv.49.2021.09.06.11.53.27 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 06 Sep 2021 11:53:29 -0700 (PDT) Sender: Guenter Roeck To: David Hildenbrand , Andrew Morton , syzbot Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, syzkaller-bugs@googlegroups.com, Linus Torvalds , "Eric W. Biederman" References: <00000000000063692b05cb493f6d@google.com> <20210906103309.f4152941a9a00a27f62dbc2b@linux-foundation.org> <59af1f1c-ae77-cfec-8d8c-32368f8ffdb6@redhat.com> From: Guenter Roeck Subject: Re: [syzbot] BUG: soft lockup in handle_mm_fault (2) Message-ID: Date: Mon, 6 Sep 2021 11:53:27 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: <59af1f1c-ae77-cfec-8d8c-32368f8ffdb6@redhat.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 9/6/21 10:46 AM, David Hildenbrand wrote: > On 06.09.21 19:33, Andrew Morton wrote: >> (cc's added) >> >> On Sun, 05 Sep 2021 18:05:40 -0700 syzbot wrote: >> >>> Hello, >>> >>> syzbot found the following issue on: >>> >>> HEAD commit:    49624efa65ac Merge tag 'denywrite-for-5.15' of git://githu.. >>> git tree:       upstream >>> console output: https://syzkaller.appspot.com/x/log.txt?x=12eff4b3300000 >>> kernel config:  https://syzkaller.appspot.com/x/.config?x=c598149362d97396 >>> dashboard link: https://syzkaller.appspot.com/bug?extid=aa7a876b8108f1622bc3 >>> compiler:       aarch64-linux-gnu-gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.1 >>> userspace arch: arm64 >>> >>> Unfortunately, I don't have any reproducer for this issue yet. >>> >>> IMPORTANT: if you fix the issue, please add the following tag to the commit: >>> Reported-by: syzbot+aa7a876b8108f1622bc3@syzkaller.appspotmail.com >>> >>> watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [syz-executor.1:26449] >>> Modules linked in: >>> irq event stamp: 248 >>> hardirqs last  enabled at (247): [] __exit_to_kernel_mode arch/arm64/kernel/entry-common.c:81 [inline] >>> hardirqs last  enabled at (247): [] exit_to_kernel_mode+0x38/0x230 arch/arm64/kernel/entry-common.c:91 >>> hardirqs last disabled at (248): [] enter_el1_irq_or_nmi+0x10/0x20 arch/arm64/kernel/entry-common.c:227 >>> softirqs last  enabled at (182): [] _stext+0x964/0xff8 >>> softirqs last disabled at (41): [] do_softirq_own_stack include/asm-generic/softirq_stack.h:10 [inline] >>> softirqs last disabled at (41): [] invoke_softirq kernel/softirq.c:439 [inline] >>> softirqs last disabled at (41): [] __irq_exit_rcu+0x208/0x4f0 kernel/softirq.c:636 >>> CPU: 0 PID: 26449 Comm: syz-executor.1 Not tainted 5.14.0-syzkaller-09416-g49624efa65ac #0 >>> Hardware name: linux,dummy-virt (DT) >>> pstate: 00000005 (nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) >>> pc : clear_page+0x14/0x28 arch/arm64/lib/clear_page.S:23 >>> lr : clear_highpage include/linux/highmem.h:181 [inline] >>> lr : kernel_init_free_pages.part.0+0x6c/0x17c mm/page_alloc.c:1286 >>> sp : ffff800019be75e0 >>> x29: ffff800019be75e0 x28: 0000000000000000 x27: 0000000000000000 >>> x26: ffff000009d64940 x25: ffff6000013ac928 x24: 00000000000014c0 >>> x23: ffff000009d63480 x22: fffffc0000173340 x21: ffff800015794a78 >>> x20: dfff800000000000 x19: fffffc0000173300 x18: 0000000000000000 >>> x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000 >>> x14: 1ffff0000337ce86 x13: 0000000000000013 x12: ffff7f800002e667 >>> x11: 1fffff800002e666 x10: ffff7f800002e666 x9 : 0000000000000000 >>> x8 : ffff600000b99a00 x7 : 0000000000000000 x6 : 000000000000003f >>> x5 : 0000000000000040 x4 : 1ffff00003060d98 x3 : 1fffe000013ac691 >>> x2 : 0000000000000004 x1 : 0000000000000040 x0 : ffff000005ccc880 >>> Call trace: >>>   clear_page+0x14/0x28 arch/arm64/lib/clear_page.S:21 >>>   kernel_init_free_pages mm/page_alloc.c:1283 [inline] >>>   post_alloc_hook+0x1ac/0x25c mm/page_alloc.c:2426 >>>   prep_new_page mm/page_alloc.c:2436 [inline] >>>   get_page_from_freelist+0x184c/0x2320 mm/page_alloc.c:4168 >>>   __alloc_pages+0x1a8/0x21d0 mm/page_alloc.c:5390 >>>   alloc_pages_vma+0xbc/0x530 mm/mempolicy.c:2252 >>>   alloc_zeroed_user_highpage_movable+0x9c/0xd0 arch/arm64/mm/fault.c:926 >>>   do_anonymous_page mm/memory.c:3767 [inline] >>>   handle_pte_fault mm/memory.c:4556 [inline] >>>   __handle_mm_fault+0xbc4/0x2210 mm/memory.c:4693 >>>   handle_mm_fault+0x1dc/0x4f0 mm/memory.c:4791 >>>   __do_page_fault arch/arm64/mm/fault.c:499 [inline] >>>   do_page_fault+0x230/0x8c0 arch/arm64/mm/fault.c:599 >>>   do_translation_fault+0x1a4/0x210 arch/arm64/mm/fault.c:680 >>>   do_mem_abort+0x64/0x1c0 arch/arm64/mm/fault.c:813 >>>   el0_da+0x7c/0x2b0 arch/arm64/kernel/entry-common.c:481 >>>   el0t_64_sync_handler+0x168/0x1b0 arch/arm64/kernel/entry-common.c:616 >>>   el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:572 > > At first sight, looks unrelated. Being stuck in clear_page() is weird; we're running inside a VM ("dummy-virt"), whereby such stuck tasks in the guests are sometimes the result of the hypervisor being stuck (e.g., heavily overcommitted). > Unrelated to your series, yes, because it was first reported after commit ebf435d3b51b ("Merge tag 'staging-5.15-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging") which predates your series. > If we don't get a reproducer, that's most probably the root cause. Let's see. > That seems unlikely. The problem was seen 8 times by now, starting September 2. Guenter