linux-kernel - Re: [PATCH v9 01/10] iomap: stash iomap read ctx in the private field of iomap

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: <20251119091254.GA24902@lst.de>
Date: Wed, 19 Nov 2025 10:12:55 +0100
From: Christoph Hellwig <hch@....de>
To: Gao Xiang <hsiangkao@...ux.alibaba.com>
Cc: Christoph Hellwig <hch@....de>, brauner@...nel.org, djwong@...nel.org,
	linux-fsdevel@...r.kernel.org, linux-erofs@...ts.ozlabs.org,
	linux-kernel@...r.kernel.org, Chao Yu <chao@...nel.org>,
	Amir Goldstein <amir73il@...il.com>,
	Joanne Koong <joannelkoong@...il.com>,
	Hongbo Li <lihongbo22@...wei.com>
Subject: Re: [PATCH v9 01/10] iomap: stash iomap read ctx in the private
 field of iomap_iter

On Wed, Nov 19, 2025 at 02:17:07PM +0800, Gao Xiang wrote:
> Hongbo didn't Cc you on this thread (I think he just added
> recipients according to MAINTAINERS), but I know you played
> a key role in iomap development, so I think you should be
> in the loop about the iomap change too.
>
> Could you give some comments (maybe review) on this patch
> if possible?  My own opinion is that if the first two
> patches can be applied in the next cycle (6.19) (I understand
> it will be too late for the whole feature into 6.19) , it
> would be very helpful to us so at least the vfs iomap branch
> won't be coupled anymore if the first two patch can be landed
> in advance.

The patch itself looks fine.  But as Darrick said we really need
to get our house in order for the iomap branch so that it actually
works this close to the merge window.