linux-kernel - Re: [PATCH v3 00/10] IOMMU memory observability

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: Thu, 4 Jan 2024 16:31:17 +0100
From: Michal Koutný <mkoutny@...e.com>
To: Pasha Tatashin <pasha.tatashin@...een.com>
Cc: akpm@...ux-foundation.org, alim.akhtar@...sung.com, 
	alyssa@...enzweig.io, asahi@...ts.linux.dev, baolu.lu@...ux.intel.com, 
	bhelgaas@...gle.com, cgroups@...r.kernel.org, corbet@....net, david@...hat.com, 
	dwmw2@...radead.org, hannes@...xchg.org, heiko@...ech.de, iommu@...ts.linux.dev, 
	jernej.skrabec@...il.com, jonathanh@...dia.com, joro@...tes.org, 
	krzysztof.kozlowski@...aro.org, linux-doc@...r.kernel.org, linux-fsdevel@...r.kernel.org, 
	linux-kernel@...r.kernel.org, linux-mm@...ck.org, linux-rockchip@...ts.infradead.org, 
	linux-samsung-soc@...r.kernel.org, linux-sunxi@...ts.linux.dev, linux-tegra@...r.kernel.org, 
	lizefan.x@...edance.com, marcan@...can.st, mhiramat@...nel.org, m.szyprowski@...sung.com, 
	paulmck@...nel.org, rdunlap@...radead.org, robin.murphy@....com, samuel@...lland.org, 
	suravee.suthikulpanit@....com, sven@...npeter.dev, thierry.reding@...il.com, tj@...nel.org, 
	tomas.mudrunka@...il.com, vdumpa@...dia.com, wens@...e.org, will@...nel.org, 
	yu-cheng.yu@...el.com, rientjes@...gle.com
Subject: Re: [PATCH v3 00/10] IOMMU memory observability

Hello.

On Tue, Dec 26, 2023 at 08:01:55PM +0000, Pasha Tatashin <pasha.tatashin@...een.com> wrote:
> This patch series solves this problem by adding both observability to
> all pages that are allocated by IOMMU, and also accountability, so
> admins can limit the amount if via cgroups.

Maybe this is a mismatch in vocabulary what you mean by the verb
"limit". But I don't see in the patchset that the offending pages would
be allocated with GFP_ACCOUNT. So the result is that the pages are
accounted (you can view the amount in memory.stat) but they are not
subject to memcg limits.

Is that what you intend?


Regards,
Michal

Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)