| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <165044753398.180787.4069543281631212706.b4-ty@kernel.org>
Date: Wed, 20 Apr 2022 13:31:21 +0100
From: Will Deacon <will@...nel.org>
To: joro@...tes.org, jgg@...pe.ca, robin.murphy@....com,
Nicolin Chen <nicolinc@...dia.com>, jean-philippe@...aro.org
Cc: catalin.marinas@....com, kernel-team@...roid.com,
Will Deacon <will@...nel.org>, stable@...r.kernel.org,
jacob.jun.pan@...ux.intel.com,
linux-arm-kernel@...ts.infradead.org, fenghua.yu@...el.com,
iommu@...ts.linux-foundation.org, rikard.falkeborn@...il.com,
linux-kernel@...r.kernel.org, baolu.lu@...ux.intel.com
Subject: Re: [PATCH] iommu/arm-smmu-v3: Fix size calculation in arm_smmu_mm_invalidate_range()
On Tue, 19 Apr 2022 14:01:58 -0700, Nicolin Chen wrote:
> The arm_smmu_mm_invalidate_range function is designed to be called
> by mm core for Shared Virtual Addressing purpose between IOMMU and
> CPU MMU. However, the ways of two subsystems defining their "end"
> addresses are slightly different. IOMMU defines its "end" address
> using the last address of an address range, while mm core defines
> that using the following address of an address range:
>
> [...]
Applied to will (for-joerg/arm-smmu/fixes), thanks!
[1/1] iommu/arm-smmu-v3: Fix size calculation in arm_smmu_mm_invalidate_range()
https://git.kernel.org/will/c/95d4782c34a6
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
Powered by blists - more mailing lists