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] [day] [month] [year] [list]
Date:   Mon, 24 Apr 2023 11:44:58 +0200
From:   Jan Kara <jack@...e.cz>
To:     Ritesh Harjani <ritesh.list@...il.com>
Cc:     Jan Kara <jack@...e.cz>, linux-fsdevel@...r.kernel.org,
        linux-ext4@...r.kernel.org, Christoph Hellwig <hch@...radead.org>,
        "Darrick J . Wong" <djwong@...nel.org>,
        Ojaswin Mujoo <ojaswin@...ux.ibm.com>,
        Disha Goel <disgoel@...ux.ibm.com>, Ted Tso <tytso@....edu>
Subject: Re: [PATCHv6 0/9] ext2: DIO to use iomap

On Fri 21-04-23 17:35:47, Ritesh Harjani wrote:
> Jan Kara <jack@...e.cz> writes:
> > them. The series has an ext4 cleanup (patch 3) and three iomap patches
> 
> Also Patch-3 is on top of ext4 journalled data patch series of yours,
> otheriwse we might see a minor merge conflict.
> 
> https://lore.kernel.org/all/20230329154950.19720-6-jack@suse.cz/

Yes, I have noticed :)

> > I guess I won't rush this for the coming merge window (unless Linus decides
> > to do rc8) but once we settle on the merge strategy I'll push out some
> 
> Ok.
> 
> > branch on which we can base further ext2 iomap conversion work.
> >
> 
> Sure, will this branch also gets reflected in linux-next for wider testing?

Yes, the branch I'll push the ext2+ext4 patches to will be included in
linux-next (I'll merge it to for-next branch).

								Honza
-- 
Jan Kara <jack@...e.com>
SUSE Labs, CR

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ