linux-kernel - Re: [PATCH v2 6/6] alloc_tag: config to store page allocation tag refs in page flags

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: <ZtfDiH3lZ9ozxm0v@casper.infradead.org>
Date: Wed, 4 Sep 2024 03:18:48 +0100
From: Matthew Wilcox <willy@...radead.org>
To: John Hubbard <jhubbard@...dia.com>
Cc: Suren Baghdasaryan <surenb@...gle.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	kent.overstreet@...ux.dev, corbet@....net, arnd@...db.de,
	mcgrof@...nel.org, rppt@...nel.org, paulmck@...nel.org,
	thuth@...hat.com, tglx@...utronix.de, bp@...en8.de,
	xiongwei.song@...driver.com, ardb@...nel.org, david@...hat.com,
	vbabka@...e.cz, mhocko@...e.com, hannes@...xchg.org,
	roman.gushchin@...ux.dev, dave@...olabs.net,
	liam.howlett@...cle.com, pasha.tatashin@...een.com,
	souravpanda@...gle.com, keescook@...omium.org, dennis@...nel.org,
	yuzhao@...gle.com, vvvvvv@...gle.com, rostedt@...dmis.org,
	iamjoonsoo.kim@....com, rientjes@...gle.com, minchan@...gle.com,
	kaleshsingh@...gle.com, linux-doc@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
	linux-mm@...ck.org, linux-modules@...r.kernel.org,
	kernel-team@...roid.com
Subject: Re: [PATCH v2 6/6] alloc_tag: config to store page allocation tag
 refs in page flags

On Tue, Sep 03, 2024 at 06:25:52PM -0700, John Hubbard wrote:
> The more I read this story, the clearer it becomes that this should be
> entirely done by the build system: set it, or don't set it, automatically.
> 
> And if you can make it not even a kconfig item at all, that's probably even
> better.
> 
> And if there is no way to set it automatically, then that probably means
> that the feature is still too raw to unleash upon the world.

I'd suggest that this implementation is just too whack.

What if you use a maple tree for this?  For each allocation range, you
can store a pointer to a tag instead of storing an index in each folio.