From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.8bytes.org (mail.8bytes.org [85.214.250.239]) by smtp.subspace.kernel.org (Postfix) with ESMTP id A10F929AB for ; Thu, 13 Jun 2024 09:16:34 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=85.214.250.239 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1718270196; cv=none; b=Ymk0GNI7f88KFXInzs9zUaSSvfovJ25izQXcPu8dJnCabhshtcFVvcOGuzSju4t2ZSJHyGTPA0RGI4dr5al7MIoAv2mqHmGmgcKrLsi4fzHx4syo4kOo+tFJfsttXiYHBk+R81nfrpMuTSRH+QMnTLKrDLGEY8B8aHc9JJhRYGc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1718270196; c=relaxed/simple; bh=LPWIOse+YFlkFcyvFtEOOyBQYQP0Mbqf1JcsJOhIcyY=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=Djz+xbF83dUIA3ENZjV+vp6CCfPKFQO/3DsovVVHyMPrSQ8Q9IpY/UwNRrpHUO15NTpIpf95Mlrs2PT0+E6Ky2VU00pfWBkt3336jI1G3HRNdBhhQZC3/OVpcY7UCzCdfm58fGzXCTlGt1z0y8Xb1Rv6cCcyBWdkt25191AV5kU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=8bytes.org; spf=pass smtp.mailfrom=8bytes.org; dkim=pass (2048-bit key) header.d=8bytes.org header.i=@8bytes.org header.b=L2ztk/XA; arc=none smtp.client-ip=85.214.250.239 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=8bytes.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=8bytes.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=8bytes.org header.i=@8bytes.org header.b="L2ztk/XA" Received: from 8bytes.org (pd9fe9dd8.dip0.t-ipconnect.de [217.254.157.216]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.8bytes.org (Postfix) with ESMTPSA id 944641C0BD3; Thu, 13 Jun 2024 11:16:33 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=8bytes.org; s=default; t=1718270193; bh=LPWIOse+YFlkFcyvFtEOOyBQYQP0Mbqf1JcsJOhIcyY=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=L2ztk/XAasnW7MKlKOWfczlO6ccl+jh2A0pPkt1uASxflfNLfpYHs/WKirS3KUcP5 7Af0W0cyPjiRQ/F/T7xD/IiXOw1GYvyKCOTeoL+B+IPp7dAwTFinzEBuwHIXLC5Yov tiMaAe/FbMPy/jAbYugNzEmj/L/EptP9EUqyr1p7u8GhM+HyGN08sBlphaFAb+T+Ac N8RquNzqdn8G1omybxKNrlblmPZSp0REhvowKAwxF4i7AX9rw/Fx603sCiwZV1JE1p fExx7QpHCwskIQyiYWK8E2SPXhWxqZI4j7R81NaQckZVzvCGFepQBReaCMvqL9yo1a rieuqifrIts7g== Date: Thu, 13 Jun 2024 11:16:32 +0200 From: Joerg Roedel To: Dimitri Sivanich Cc: Yi Zhang , "Tian, Kevin" , Vasant Hegde , Baolu Lu , Suravee Suthikulpanit , Will Deacon , Robin Murphy , David Wang <00107082@163.com>, Shinichiro Kawasaki , iommu@lists.linux.dev, linux-kernel@vger.kernel.org, Steve Wahl , Russ Anderson Subject: Re: [PATCH] iommu/amd: Fix panic accessing amd_iommu_enable_faulting Message-ID: References: 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 Thu, May 30, 2024 at 01:36:03PM -0500, Dimitri Sivanich wrote: > This fixes a bug introduced by commit d74169ceb0d2 ("iommu/vt-d: Allocate > DMAR fault interrupts locally"). The panic happens when > amd_iommu_enable_faulting is called from CPUHP_AP_ONLINE_DYN context. > > Fixes: d74169ceb0d2 ("iommu/vt-d: Allocate DMAR fault interrupts locally") > Signed-off-by: Dimitri Sivanich > Tested-by: Yi Zhang > --- > drivers/iommu/amd/init.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) Applied to iommu/fixes, thanks.