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: <e572c851-fcbb-4814-b24e-5e0e2e67c732@linux.alibaba.com>
Date: Wed, 19 Nov 2025 14:17:07 +0800
From: Gao Xiang <hsiangkao@...ux.alibaba.com>
To: Christoph Hellwig <hch@....de>
Cc: 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

Hi Christoph,

On 2025/11/19 13:49, Christoph Hellwig wrote:
> On Tue, Nov 18, 2025 at 03:35:45PM +0800, Gao Xiang wrote:
>> (... try to add Christoph..)
> 
> What are you asking me for?

Sorry about the confusion.

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.

Thanks,
Gao Xiang

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ