Received: by 2002:a89:d88:0:b0:1fa:5c73:8e2d with SMTP id eb8csp2307609lqb; Mon, 27 May 2024 15:31:57 -0700 (PDT) X-Forwarded-Encrypted: i=3; AJvYcCUUV6fUzBDinc6IKnqK5dWEofGDUVXktgKU/55yD3UHzhBBb1pNL3ppGkBzb0mWeqBpTiwrzDIxev1+d1isfgcKQb4EU0HqgorPcAaNAg== X-Google-Smtp-Source: AGHT+IEidzteXW89yOoCHKmd28DpfhDHGGjIc6RhLUVF/gW+SN68WYpvGqRvrJGR29mk4rYQzU/A X-Received: by 2002:a19:e010:0:b0:523:b371:7b78 with SMTP id 2adb3069b0e04-529644ec076mr7527827e87.13.1716849117166; Mon, 27 May 2024 15:31:57 -0700 (PDT) ARC-Seal: i=2; a=rsa-sha256; t=1716849117; cv=pass; d=google.com; s=arc-20160816; b=StQWg9xnPNF7M+zRMOArRxpyTTaEdGJbcjKHUVi3rnYPVKWy3Pjnr5Tx1FQtXBjMIM T2ZXbMSPfUpL+0/ugX4AVVewm112+JDxAXmJsSQmlHMepbcYAgcFHNQ+g2GSiPeINxgH LjnnBJU1AblokylawJICGpCFWROemhWkGG1q0XR2oibFacHFV0sT7MlnwZEbhRz/iVin UgtaNPy+d1o5FGV9Zer9t7aJXxoEVgCMjVhlxpAFsaDp76xDM83doAPszaQod3qwsOYJ KYNt0BESMF/QWO9PlE+RATN3rAchXVA05nA/M8+vKSQCGtyolBiwrGfOY6ueC2cuujmC +fQA== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:list-unsubscribe :list-subscribe:list-id:precedence:references:in-reply-to:message-id :subject:cc:to:from:date; bh=wkWViZB7Ah651duBPihx5UnuKf/7BzqehDIFlTgrTnI=; fh=xSbff4mA9pXr9ObRe+vMESKf8yjS6n+NF5Rqcg4k4HA=; b=stM49B0plbw6x6GMMZ7Zp4zgbwPBP3G79wrsx0YvDc2zirLDvhSjuCCRvK8n1fJ+Ub uk3UEeG/ChAUL3enawugIEXcZhLD3weIdvKYvsXeCE3u+n3g3mE0mapX9FEGmpo4OzC3 v7mRDYESpj2Ylxo9yQWb+6020zSGUyG+9qyAG3/jq7fz+tIaGw4jmAFRCy4id0/LtbFT ZyI7vTAG7K4XknBhDol8So7tUmqpXyxN5siHtd5xIkpKOSdNtGfDKUOgPYD75oQ+N7d6 jn+3EsTugNYQ1T8YBGR+0d7eC7vAFTuNgbkbb+ZQODeCQNoMdnVGjAKxrqRSgCVmOPow f30g==; dara=google.com ARC-Authentication-Results: i=2; mx.google.com; arc=pass (i=1); spf=pass (google.com: domain of linux-kernel+bounces-191493-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) smtp.mailfrom="linux-kernel+bounces-191493-linux.lists.archive=gmail.com@vger.kernel.org" Return-Path: Received: from am.mirrors.kernel.org (am.mirrors.kernel.org. [2604:1380:4601:e00::3]) by mx.google.com with ESMTPS id a640c23a62f3a-a626cc36e6bsi434282166b.375.2024.05.27.15.31.57 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 27 May 2024 15:31:57 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel+bounces-191493-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3; Authentication-Results: mx.google.com; arc=pass (i=1); spf=pass (google.com: domain of linux-kernel+bounces-191493-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) smtp.mailfrom="linux-kernel+bounces-191493-linux.lists.archive=gmail.com@vger.kernel.org" Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by am.mirrors.kernel.org (Postfix) with ESMTPS id DD3191F2227C for ; Mon, 27 May 2024 22:31:56 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 4FB23167DB5; Mon, 27 May 2024 22:31:44 +0000 (UTC) Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B5BB815FD10; Mon, 27 May 2024 22:31:43 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1716849103; cv=none; b=Cg3cCsy62s6G7g1zwvqmpzEFqFHQS0fwPpPhzrSHDRpxG+7X6WfEPo7dsyhD3N8KPN5NIvKCwI90F7OEgZ6mRqQjamAPfj3t2TPrAxHoWBJjz5w11P4FZwFkroRg/bjP7Vf0USZHkSgyArlg3294MYsnXQYNapCEB5JLoe0UCF8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1716849103; c=relaxed/simple; bh=wkWViZB7Ah651duBPihx5UnuKf/7BzqehDIFlTgrTnI=; h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=c2lX6KbTJHrD6n8fG18e+4wy5tYXYEFOls1ZLyj1d1gRQ0WlOjjsSW8OVNoADfiaRQu5kmvWSO03BHGozep9OqjAP7qgW1ZrYpAHj+UkLSEe1qQVDNHUJsDTIQNKmJUGTTpV1aluHn4KfWdujdq4n0jRjaKm6aHZ/S00bM0n43E= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 Received: by smtp.kernel.org (Postfix) with ESMTPSA id B42C4C2BBFC; Mon, 27 May 2024 22:31:41 +0000 (UTC) Date: Mon, 27 May 2024 18:31:39 -0400 From: Steven Rostedt To: "Linux regression tracking (Thorsten Leemhuis)" Cc: Linux regressions mailing list , Ilkka =?UTF-8?B?TmF1bGFww6TDpA==?= , stable@vger.kernel.org, linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org Subject: Re: Bug in Kernel 6.8.x, 6.9.x Causing Trace/Panic During Shutdown/Reboot Message-ID: <20240527183139.42b6123c@rorschach.local.home> In-Reply-To: <5b79732b-087c-411f-a477-9b837566673e@leemhuis.info> References: <5b79732b-087c-411f-a477-9b837566673e@leemhuis.info> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-pc-linux-gnu) Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Fri, 24 May 2024 12:50:08 +0200 "Linux regression tracking (Thorsten Leemhuis)" wrote: > > - Affected Versions: Before kernel version 6.8.10, the bug caused a > > quick display of a kernel trace dump before the shutdown/reboot > > completed. Starting from version 6.8.10 and continuing into version > > 6.9.0 and 6.9.1, this issue has escalated to a kernel panic, > > preventing the shutdown or reboot from completing and leaving the > > machine stuck. You state "Before kernel version 6.8.10, the bug caused ...". Does that mean that a bug was happening before v6.8.10? But did not cause a panic? I just noticed your second screen shot from your report, and it has: "cache_from_obj: Wrong slab cache, tracefs_inode_cache but object is from inode_cache" So somehow an tracefs_inode was allocated from the inode_cache and is now being freed by the tracefs_inode logic? Did this happen before 6.8.10? If so, this code could just be triggering an issue from an unrelated bug. Thanks, -- Steve