linux-kernel - Re: [PATCH -mm 1/2] SPARC64: add the segment boundary checking to IOMMUs while merging SG entries

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]

Date:	Sat, 22 Mar 2008 17:23:05 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	fujita.tomonori@....ntt.co.jp
Cc:	linux-kernel@...r.kernel.org, linux-sparc@...r.kernel.org,
	tomof@....org, akpm@...ux-foundation.org
Subject: Re: [PATCH -mm 1/2] SPARC64: add the segment boundary checking to
 IOMMUs while merging SG entries

From: FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
Date: Thu, 13 Mar 2008 12:47:06 +0900

> Some IOMMUs allocate memory areas spanning LLD's segment boundary
> limit. It forces low level drivers to have a workaround to adjust
> scatter lists that the IOMMU builds. We are in the process of making
> all the IOMMUs respect the segment boundary limits to remove such work
> around in LLDs.
> 
> SPARC64 IOMMUs were rewritten to use the IOMMU helper functions and
> the commit 89c94f2f70d093f59b55d3ea8042d13889169346 made the IOMMUs
> not allocate memory areas spanning the segment boundary limit.
> 
> However, SPARC64 IOMMUs allocate memory areas first then try to merge
> them (while some IOMMUs walk through all the sg entries to see how
> they can be merged first and allocate memory areas). So SPARC64 IOMMUs
> also need the boundary limit checking when they try to merge sg
> entries.
> 
> Signed-off-by: FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>

Acked-by: David S. Miller <davem@...emloft.net>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/