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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4762BCDB482 for ; Tue, 17 Oct 2023 14:17:01 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1343675AbjJQORB (ORCPT ); Tue, 17 Oct 2023 10:17:01 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39866 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234998AbjJQORA (ORCPT ); Tue, 17 Oct 2023 10:17:00 -0400 Received: from desiato.infradead.org (desiato.infradead.org [IPv6:2001:8b0:10b:1:d65d:64ff:fe57:4e05]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 46F7CFD; Tue, 17 Oct 2023 07:16:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=desiato.20200630; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=ZrpZDwfysdaLF96tjupfAFmYhqWMtpjSOZplJCsp7DI=; b=A2XvqQfwa4LL9+gK+9c6c+t90e X04jGQ5YO+KFT3QdjPV5ARmMkuNS3t2K+vO/TqdSmH7dLaxZp3wF9gy76rGMupD79KrE+2lQiRlmk L4f9p7WpYHrC1oUAR/Fc3qL9+BMrIVEGcjNSxo8FhfFsba8jy3uL9f2DgIJn99CYsnrNxlqu7oVb2 3a1Qy004P5+Lw/pbszbyfSb2KGpTOU1JSwmqd7rE9d3frS+zpiIKOQ6D2OxjX96Ud0nQ7+dijbqc5 hIiKEyanq1E8zjfYZabzKcfDOFek4MGYzlrqbuj92XXtRREiYHSMYYXg/yKo45vjKOZfb9Yval5S/ ksfpsP2w==; Received: from j130084.upc-j.chello.nl ([24.132.130.84] helo=noisy.programming.kicks-ass.net) by desiato.infradead.org with esmtpsa (Exim 4.96 #2 (Red Hat Linux)) id 1qsksN-0079Qq-0F; Tue, 17 Oct 2023 14:16:51 +0000 Received: by noisy.programming.kicks-ass.net (Postfix, from userid 1000) id BC7A7300194; Tue, 17 Oct 2023 16:16:50 +0200 (CEST) Date: Tue, 17 Oct 2023 16:16:50 +0200 From: Peter Zijlstra To: syzbot Cc: adilger.kernel@dilger.ca, bsegall@google.com, dvyukov@google.com, linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, nogikh@google.com, syzkaller-bugs@googlegroups.com, tglx@linutronix.de, tytso@mit.edu Subject: Re: [syzbot] [ext4?] possible deadlock in console_flush_all (2) Message-ID: <20231017141650.GC1599@noisy.programming.kicks-ass.net> References: <000000000000e40a2906072e9567@google.com> <000000000000bc00ea0607e9359d@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000000000000bc00ea0607e9359d@google.com> Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org On Tue, Oct 17, 2023 at 06:07:50AM -0700, syzbot wrote: > syzbot has found a reproducer for the following issue on: > > HEAD commit: 213f891525c2 Merge tag 'probes-fixes-v6.6-rc6' of git://gi.. > list_add corruption. next->prev should be prev (ffff8880b993d228), but was caff904900000000. (next=ffff8880783659f8). Urgh, I've not seen that happen before. How reliable does this trigger? > __list_add_valid_or_report+0xa2/0x100 lib/list_debug.c:29 > __list_add_valid include/linux/list.h:88 [inline] > __list_add include/linux/list.h:150 [inline] > list_add include/linux/list.h:169 [inline] > account_entity_enqueue kernel/sched/fair.c:3534 [inline] > enqueue_entity+0x97b/0x1490 kernel/sched/fair.c:5117 > enqueue_task_fair+0x15b/0xbc0 kernel/sched/fair.c:6536 > enqueue_task kernel/sched/core.c:2102 [inline] > activate_task kernel/sched/core.c:2132 [inline] > ttwu_do_activate+0x214/0xd90 kernel/sched/core.c:3787 > ttwu_queue kernel/sched/core.c:4029 [inline] > try_to_wake_up+0x8e7/0x15b0 kernel/sched/core.c:4346 > autoremove_wake_function+0x16/0x150 kernel/sched/wait.c:424 > __wake_up_common+0x140/0x5a0 kernel/sched/wait.c:107 > __wake_up_common_lock+0xd6/0x140 kernel/sched/wait.c:138 > wake_up_klogd_work_func kernel/printk/printk.c:3840 [inline] > wake_up_klogd_work_func+0x90/0xa0 kernel/printk/printk.c:3829 > irq_work_single+0x1b5/0x260 kernel/irq_work.c:221 > irq_work_run_list kernel/irq_work.c:252 [inline] > irq_work_run_list+0x92/0xc0 kernel/irq_work.c:235 > update_process_times+0x1d5/0x220 kernel/time/timer.c:2074 > tick_sched_handle+0x8e/0x170 kernel/time/tick-sched.c:254 > tick_sched_timer+0xe9/0x110 kernel/time/tick-sched.c:1492 > __run_hrtimer kernel/time/hrtimer.c:1688 [inline] > __hrtimer_run_queues+0x647/0xc10 kernel/time/hrtimer.c:1752 > hrtimer_interrupt+0x31b/0x800 kernel/time/hrtimer.c:1814 > local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1063 [inline] > __sysvec_apic_timer_interrupt+0x105/0x3f0 arch/x86/kernel/apic/apic.c:1080 > sysvec_apic_timer_interrupt+0x8e/0xc0 arch/x86/kernel/apic/apic.c:1074 >