linux-ext4 - Re: fiemap cleanups v4

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: <20200524115706.GA1800@lst.de>
Date:   Sun, 24 May 2020 13:57:06 +0200
From:   Christoph Hellwig <hch@....de>
To:     Al Viro <viro@...iv.linux.org.uk>
Cc:     Christoph Hellwig <hch@....de>, linux-ext4@...r.kernel.org,
        jack@...e.cz, tytso@....edu, adilger@...ger.ca,
        riteshh@...ux.ibm.com, amir73il@...il.com,
        linux-fsdevel@...r.kernel.org, linux-unionfs@...r.kernel.org
Subject: Re: fiemap cleanups v4

On Sat, May 23, 2020 at 04:52:16PM +0100, Al Viro wrote:
> Hmmm...  I can do an immutable shared branch, no problem.  What would
> you prefer for a branchpoint for that one?

This needs pretty much latest Linus' tree as it sits on top of the bug
fixes merged this week.  But then again I'm not sure we even need
a shared tree, as there shouldn't be any conflicts.  But looking at
linux-next it seems Ted has actually pulled in the whole series, so
I think we actually are done.

But while I've got you attention:  Can you take a look at my
"clean up kernel_{read,write} & friends v2" series?