From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx.socionext.com (mx.socionext.com [202.248.49.38]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 3BAA62D8DDD for ; Wed, 21 Jan 2026 11:05:09 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=202.248.49.38 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768993513; cv=none; b=ayi2A4/KBBnXD6Pza1JiqTbdJcLCS0+W8z3djjrHted/A8I4z163ijTiLCLCO0dEOWGoVp9DHdpHetlkWmoMNhVsdV/NCvzkUPtBC5ArJFkhz8WmCVLzN3Reg+8MK5UxTTbAWZknKkpCliwgpI/7hg7iVCskURqkyYBMepjAttI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768993513; c=relaxed/simple; bh=eezuRGoxXuRYKtLQ/9I2o1c2Kbh+5AybBP30dipSIzw=; h=Message-ID:Date:MIME-Version:From:Subject:To:Cc:Content-Type; b=HZoZwoaSsZR3mLoJ8lDp7/Z6IoADhhhFQKs+xczb3+m4e1V11zE/DlkWyAOedJyDcI53bB80PO2wbWMq0f5K7BlDBIpUumE8aKRYc7XLtmgyPKJfRqJn67/4O7aZbYQkM6RfBmwElSy5TwxLNyY4OivwzjmS07gDW+vC/aniupk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=socionext.com; spf=pass smtp.mailfrom=socionext.com; arc=none smtp.client-ip=202.248.49.38 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=socionext.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=socionext.com Received: from unknown (HELO kinkan3-ex.css.socionext.com) ([172.31.9.52]) by mx.socionext.com with ESMTP; 21 Jan 2026 20:03:59 +0900 Received: from mail.mfilter.local (mail-arc02.css.socionext.com [10.213.46.40]) by kinkan3-ex.css.socionext.com (Postfix) with ESMTP id 02E0E2069FE9; Wed, 21 Jan 2026 20:03:59 +0900 (JST) Received: from iyokan3.css.socionext.com ([172.31.9.53]) by m-FILTER with ESMTP; Wed, 21 Jan 2026 20:03:58 +0900 Received: from [10.212.247.110] (unknown [10.212.247.110]) by iyokan3.css.socionext.com (Postfix) with ESMTP id 8FE3A1071A3; Wed, 21 Jan 2026 20:03:58 +0900 (JST) Message-ID: Date: Wed, 21 Jan 2026 20:04:03 +0900 Precedence: bulk X-Mailing-List: stable@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird From: Kunihiko Hayashi Subject: [REGRESSION] v6.6.120: i3c crash caused by commit 82a09b9965ed To: stable@vger.kernel.org Cc: Frank Li , Alexandre Belloni , Greg Kroah-Hartman , Sasha Levin Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Dear stable maintainers, After updating from v6.6.119 to v6.6.120, I noticed a kernel crash when I3C was enabled. This regression is caused by: commit 82a09b9965ed ("i3c: fix refcount inconsistency in i3c_master_register") The issue is resolved when the following upstream fix commit is applied: commit 3502cea99c7c ("i3c: Move device name assignment after i3c_bus_init") I also confirmed that commit 82a09b9965ed is applied to other stable trees, including at least linux-6.1.y, so the same regression may affect them as well. Applying the fix commit or reverting 82a09b9965ed resolves the issue. Thank you, --- Best Regards Kunihiko Hayashi