linux-kernel - Re: [PATCH v5 00/11] 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 for Android: free password hash cracker in your pocket

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

Date: Fri, 15 Mar 2024 22:53:20 +0100
From: Joerg Roedel <joro@...tes.org>
To: David Rientjes <rientjes@...gle.com>
Cc: Pasha Tatashin <pasha.tatashin@...een.com>,
	Andrew Morton <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, 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, bagasdotme@...il.com,
	mkoutny@...e.com
Subject: Re: [PATCH v5 00/11] IOMMU memory observability

Hi David,

On Fri, Mar 15, 2024 at 02:33:53PM -0700, David Rientjes wrote:
> Joerg, is this series anticipated to be queued up in the core branch of 
> git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git so it gets into 
> linux-next?
> 
> This observability seems particularly useful so that we can monitor and 
> alert on any unexpected increases (unbounded memory growth from this 
> subsystem has in the past caused us issues before the memory is otherwise 
> not observable by host software).
> 
> Or are we still waiting on code reviews from some folks that we should 
> ping?

A few more reviews would certainly help, but I will also do a review on
my own. If things are looking good I can merge it into the iommu tree
when 6.9-rc3 is released (which is the usual time I start merging new
stuff).

Regards,

	Joerg