[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <173021496151.4097715.14758035881649445798.b4-ty@kernel.org>
Date: Tue, 29 Oct 2024 16:15:13 +0000
From: Will Deacon <will@...nel.org>
To: Pratyush Brahma <quic_pbrahma@...cinc.com>
Cc: catalin.marinas@....com,
kernel-team@...roid.com,
Will Deacon <will@...nel.org>,
robin.murphy@....com,
joro@...tes.org,
jgg@...pe.ca,
jsnitsel@...hat.com,
robdclark@...omium.org,
quic_c_gdjako@...cinc.com,
dmitry.baryshkov@...aro.org,
linux-arm-kernel@...ts.infradead.org,
iommu@...ts.linux.dev,
linux-kernel@...r.kernel.org,
quic_charante@...cinc.com,
stable@...r.kernel.org,
Prakash Gupta <quic_guptap@...cinc.com>
Subject: Re: [PATCH v2] iommu/arm-smmu: Defer probe of clients after smmu device bound
On Fri, 04 Oct 2024 14:34:28 +0530, Pratyush Brahma wrote:
> Null pointer dereference occurs due to a race between smmu
> driver probe and client driver probe, when of_dma_configure()
> for client is called after the iommu_device_register() for smmu driver
> probe has executed but before the driver_bound() for smmu driver
> has been called.
>
> Following is how the race occurs:
>
> [...]
Applied to will (for-joerg/arm-smmu/updates), thanks!
[1/1] iommu/arm-smmu: Defer probe of clients after smmu device bound
https://git.kernel.org/will/c/229e6ee43d2a
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
Powered by blists - more mailing lists