linux-kernel - Re: [v2 PATCH] iommu/arm-smmu-v3: Fix L1 stream table index calculation for 32-bit sid size

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <26ee77f2-720d-4e16-9f6c-fa15fd13d305@os.amperecomputing.com>
Date: Fri, 4 Oct 2024 09:05:46 -0700
From: Yang Shi <yang@...amperecomputing.com>
To: Jason Gunthorpe <jgg@...pe.ca>
Cc: Nicolin Chen <nicolinc@...dia.com>, james.morse@....com, will@...nel.org,
 robin.murphy@....com, linux-arm-kernel@...ts.infradead.org,
 linux-kernel@...r.kernel.org
Subject: Re: [v2 PATCH] iommu/arm-smmu-v3: Fix L1 stream table index
 calculation for 32-bit sid size



On 10/4/24 5:43 AM, Jason Gunthorpe wrote:
> On Thu, Oct 03, 2024 at 08:31:23AM -0700, Yang Shi wrote:
>> If I understand correctly, the check is mainly used to avoid the u64 -> u32
>> overflow. This check guarantee no overflow. If some crazy hardware really
>> requests that large memory, the allocation will fail.
> Sure, the kalloc will print a warn on anyhow if it is too big

Thank you. Will spin a new revision.

> Jason