linux-kernel - Re: [PATCH v14 00/10] erofs: Introduce page cache sharing feature

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: <20260114-komma-begeistern-20adeb35fdb8@brauner>
Date: Wed, 14 Jan 2026 16:34:46 +0100
From: Christian Brauner <brauner@...nel.org>
To: Gao Xiang <hsiangkao@...ux.alibaba.com>
Cc: chao@...nel.org, djwong@...nel.org, amir73il@...il.com, hch@....de, 
	linux-fsdevel@...r.kernel.org, linux-erofs@...ts.ozlabs.org, linux-kernel@...r.kernel.org, 
	Hongbo Li <lihongbo22@...wei.com>
Subject: Re: [PATCH v14 00/10] erofs: Introduce page cache sharing feature

On Wed, Jan 14, 2026 at 06:28:34PM +0800, Gao Xiang wrote:
> Hi Christian,
> 
> On 2026/1/12 22:40, Gao Xiang wrote:
> > Hi Christian,
> > 
> > On 2026/1/12 17:14, Christian Brauner wrote:
> > > On Fri, Jan 09, 2026 at 10:28:46AM +0000, Hongbo Li wrote:
> > > > Enabling page cahe sharing in container scenarios has become increasingly
> > > > crucial, as it can significantly reduce memory usage. In previous efforts,
> > > > Hongzhen has done substantial work to push this feature into the EROFS
> > > > mainline. Due to other commitments, he hasn't been able to continue his
> > > > work recently, and I'm very pleased to build upon his work and continue
> > > > to refine this implementation.
> > > 
> > > I can't vouch for implementation details but I like the idea so +1 from me.
> > 
> > Thanks, I think it should be fine.
> > Let me finalize the review this week.
> 
> I wonder if it's possible that you could merge v14
> PATCH 1 and 2 now to the vfs-iomap branch (both
> patches are reviewed or acked):
> https://lore.kernel.org/linux-fsdevel/20260109102856.598531-2-lihongbo22@huawei.com
> https://lore.kernel.org/linux-fsdevel/20260109102856.598531-3-lihongbo22@huawei.com
> 
> since these two patches are almost independent to the
> main feature and can be merged independently as I said
> in the previous cycle.
> 
> Merging those patches into a vfs branch also avoids
> other iomap conflicts.

Done.

> 
> For the other patches (since PATCH 3), how about going
> through erofs tree (I will merge your iomap branch),

Fine.

> since it seems at least it will cause several conflicts
> with my other ongoing work, does it sound good to you?

All good.