linux-kernel - Re: [PATCH v6 00/26] 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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <usnx4lnlazgeuvyqd5tcelb4umob4xxkvzhbv7kx2d257u5wej@bxx6ahfma5bf>
Date: Mon, 13 Jan 2025 12:05:24 +1100
From: Alistair Popple <apopple@...dia.com>
To: Dan Williams <dan.j.williams@...el.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org, 
	alison.schofield@...el.com, 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, david@...hat.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, 
	chenhuacai@...nel.org, kernel@...0n.name, loongarch@...ts.linux.dev
Subject: Re: [PATCH v6 00/26] fs/dax: Fix ZONE_DEVICE page reference counts

On Fri, Jan 10, 2025 at 07:35:57PM -0800, Dan Williams wrote:
> Andrew Morton wrote:
> > On Thu, 9 Jan 2025 23:05:56 -0800 Dan Williams <dan.j.williams@...el.com> wrote:
> > 
> > > >  - Remove PTE_DEVMAP definitions from Loongarch which were added since
> > > >    this series was initially written.
> > > [..]
> > > > 
> > > > base-commit: e25c8d66f6786300b680866c0e0139981273feba
> > > 
> > > If this is going to go through nvdimm.git I will need it against a
> > > mainline tag baseline. Linus will want to see the merge conflicts.
> > > 
> > > Otherwise if that merge commit is too messy, or you would rather not
> > > rebase, then it either needs to go one of two options:
> > > 
> > > - Andrew's tree which is the only tree I know of that can carry
> > >   patches relative to linux-next.
> > 
> > I used to be able to do that but haven't got around to setting up such
> > a thing with mm.git.  This is the first time the need has arisen,
> > really.
> 
> Oh, good to know.
> 
> > 
> > > - Wait for v6.14-rc1 
> > 
> > I'm thinking so.  Darrick's review comments indicate that we'll be seeing a v7.

I'm ok with that. It could do with a decent soak in linux-next anyway given it
touches a lot of mm and fs.

Once v6.14-rc1 is released I will do a rebase on top of that.

> > > and get this into nvdimm.git early in the cycle
> > >   when the conflict storm will be low.
> > 
> > erk.  This patchset hits mm/ a lot, and nvdimm hardly at all.  Is it
> > not practical to carry this in mm.git?
> 
> I'm totally fine with it going through mm.git. nvdimm.git is just the
> historical path for touches to fs/dax.c, and git blame points mostly to
> me for the issues Alistair is fixing. I am happy to review and ack and
> watch this go through mm.git.