linux-kernel - Re: [PATCH 00/11] Remove AS_EIO and AS

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: <20230112083057.GA14077@lst.de>
Date:   Thu, 12 Jan 2023 09:30:57 +0100
From:   Christoph Hellwig <hch@....de>
To:     "Matthew Wilcox (Oracle)" <willy@...radead.org>
Cc:     Jeff Layton <jlayton@...hat.com>, linux-fsdevel@...r.kernel.org,
        linux-mm@...ck.org, linux-kernel@...r.kernel.org,
        David Sterba <dsterba@...e.com>
Subject: Re: [PATCH 00/11] Remove AS_EIO and AS_ENOSPC

On Mon, Jan 09, 2023 at 05:18:12AM +0000, Matthew Wilcox (Oracle) wrote:
> Finish the work of converting every user to the "new" wb_err
> infrastructure.  This will clash with Christoph's patch series to remove
> folio_write_one(), so I'll redo this after that patch series goes in.

Based on the conflicts with the btrfs tree picking up the btrfs part
of this series I think the best way forward is:

 - I'll resubmit my series without the two btrfs patches and the final
   patch to move folio_write_one into jfs
 - that last patch will be delayed until 6.4 and rebased on top of
   your series

While this keeps folio_write_one/write_one_page around for one more
merge window it should entangle all the work nicely.  We'll just need
to watch out that no new users appear.