linux-kernel - Re: [PATCH v3 00/25] fs/dax: Fix ZONE

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] [day] [month] [year] [list]

Message-ID: <jn3j4pdzfnlai4oqr4g7ldl6cq6awiyugg5gbny3l3g5y67abe@rm6zpap7y2gh>
Date: Tue, 17 Dec 2024 16:20:21 +1100
From: Alistair Popple <apopple@...dia.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: David Hildenbrand <david@...hat.com>, 
	Dan Williams <dan.j.williams@...el.com>, linux-mm@...ck.org, lina@...hilina.net, zhang.lyra@...il.com, 
	gerald.schaefer@...ux.ibm.com, vishal.l.verma@...el.com, dave.jiang@...el.com, 
	logang@...tatee.com, bhelgaas@...gle.com, jack@...e.cz, jgg@...pe.ca, 
	catalin.marinas@....com, will@...nel.org, mpe@...erman.id.au, npiggin@...il.com, 
	dave.hansen@...ux.intel.com, ira.weiny@...el.com, willy@...radead.org, djwong@...nel.org, 
	tytso@....edu, linmiaohe@...wei.com, peterx@...hat.com, 
	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org, 
	linux-arm-kernel@...ts.infradead.org, linuxppc-dev@...ts.ozlabs.org, nvdimm@...ts.linux.dev, 
	linux-cxl@...r.kernel.org, linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org, 
	linux-xfs@...r.kernel.org, jhubbard@...dia.com, hch@....de, david@...morbit.com, 
	sfr@...b.auug.org.au
Subject: Re: [PATCH v3 00/25] fs/dax: Fix ZONE_DEVICE page reference counts

On Sun, Dec 15, 2024 at 10:26:55PM -0800, Andrew Morton wrote:
> On Mon, 16 Dec 2024 11:55:30 +1100 Alistair Popple <apopple@...dia.com> wrote:
> 
> > The remainder are more -mm focussed. However they do depend on the fs/dax
> > cleanups in the first half so the trick would be making sure Andrew only takes
> > them if the nvdimm.git changes have made it into -next. I'm happy with either
> > approach, so let me know if I should split the series or not.
> 
> My inclination is to put it all into the nvdimm tree, with appropriate
> MM developer acks.
> 
> But I'm having difficulty determining how practical that is because the
> v3 series is almost a month old so my test merging was quite ugly.
> 
> Perhaps you could prepare a new-doesn't-need-to-be-final version for
> people to look at and to aid with this head-scratching?

I have just sent a new-maybe-almost-final v4 rebased on top of next-20241216 to
help with the head-scratching. I haven't yet done extensive build tests or a full
xfs-test run on it yet because it sounded better to get it out sooner. So no doubt
the kernel build bot will find some fat finger of mine somewhere :-)

That said the rebase wasn't awful so let me know if it should be rebased on a
different tree.

 - Alistair