From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by smtp.subspace.kernel.org (Postfix) with ESMTP id CDF6854763 for ; Tue, 24 Feb 2026 11:07:02 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=217.140.110.172 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771931224; cv=none; b=qWoXvORK9uk7f1/khpC9DZ3D3I3GUEANsucz6xM0gW8FZx6EjOvoGgnPzJjGn3PUYLyuZbLBVfoBUcMKbEv33nMdlC8XMssvZIJKVN9FR8vro4Vd0nQcP4/I21AsMYVaOWhUN04qNtWNZF9TnhfpMaMH0c2XHO2HO4t41VAWz+k= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771931224; c=relaxed/simple; bh=Xb5Irx6Y2/0EFOC8ZKwG/ERlc7RuNp/cmMAY9HCGTq8=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=bemZX1Ru5TnJZvSyYs8qmPGbbjTKp5lOVDHA/kZXCXRlOE4NZWO4+o3S4h+YIM8/hbAvD+DNGkGmmdmdgiDbeL/g0hkdMnmneOfKEtTcQy6jaCOfzbMMckFDrD0Dhryg2SA+SGHbAE1Xb6NU+1Honpe8pAgbI/TYXT1bH21/QT0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=arm.com; spf=pass smtp.mailfrom=arm.com; arc=none smtp.client-ip=217.140.110.172 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=arm.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=arm.com Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id C35D7339; Tue, 24 Feb 2026 03:06:55 -0800 (PST) Received: from localhost (e132581.arm.com [10.1.196.87]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 9C3FF3F59E; Tue, 24 Feb 2026 03:07:01 -0800 (PST) Date: Tue, 24 Feb 2026 11:06:59 +0000 From: Leo Yan To: Suzuki K Poulose Cc: Mike Leach , James Clark , Alexander Shishkin , Greg Kroah-Hartman , Mathieu Poirier , Mao Jinlong , coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v4 0/8] coresight: Fix device registration and unregistration Message-ID: <20260224110659.GA4184494@e132581.arm.com> References: <20260209-arm_coresight_refactor_dev_register-v4-0-62d6042f76f7@arm.com> 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-Disposition: inline In-Reply-To: On Mon, Feb 23, 2026 at 01:28:03PM +0000, Suzuki K Poulose wrote: [...] > [ 827.216924] Possible unsafe locking scenario: > [ 827.216924] > [ 827.222849] CPU0 CPU1 > [ 827.227380] ---- ---- > [ 827.231912] lock(coresight_mutex); > [ 827.235491] lock(ect_mutex); > [ 827.241073] lock(coresight_mutex); > [ 827.247176] lock(ect_mutex); > [ 827.250233] > [ 827.250233] *** DEADLOCK *** Thanks for the test, Suzuki. I have sent a refactor patch to dismiss locking chain: https://lore.kernel.org/linux-arm-kernel/20260224-arm_coresight_refactor_cti_resource_release-v1-1-ff1b2bca9176@arm.com/T/#u For recording, I enabled the following configs to reproduce the lockdep report: CONFIG_LOCKUP_DETECTOR CONFIG_PROVE_LOCKING Thanks, Leo