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: <20250516121938.GA7158@mit.edu>
Date: Fri, 16 May 2025 08:19:38 -0400
From: "Theodore Ts'o" <tytso@....edu>
To: John Garry <john.g.garry@...cle.com>
Cc: "Ritesh Harjani (IBM)" <ritesh.list@...il.com>, linux-ext4@...r.kernel.org,
        Jan Kara <jack@...e.cz>, djwong@...nel.org,
        Ojaswin Mujoo <ojaswin@...ux.ibm.com>, linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH v5 7/7] ext4: Add atomic block write documentation

On Fri, May 16, 2025 at 09:55:09AM +0100, John Garry wrote:
> 
> Or move this file to a common location, and have separate sections for ext4
> and xfs? This would save having scattered files for instructions.

What is the current outook for the xfs changes landing in the next
merge window?  I haven't been tracking the latest rounds of reviews
for the xfs atomic writes patchset.

If the xfs atomic writes patchset aren't going to land this window,
then we can land them as ext4 specific documentation, and when the xfs
patches land, we can reorganize the documentation at that point.  Does
that make sense?

					- Ted

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ