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: <20170914211519.aieumj734uazwlmj@thunk.org>
Date:   Thu, 14 Sep 2017 17:15:19 -0400
From:   Theodore Ts'o <tytso@....edu>
To:     Andreas Gruenbacher <agruenba@...hat.com>
Cc:     Alexander Viro <viro@...iv.linux.org.uk>,
        linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org,
        linux-xfs@...r.kernel.org, Jan Kara <jack@...e.cz>,
        Christoph Hellwig <hch@....de>
Subject: Re: [PATCH v3 4/4] ext4: Switch to iomap for SEEK_HOLE / SEEK_DATA

On Thu, Sep 14, 2017 at 04:06:19PM +0200, Andreas Gruenbacher wrote:
> From: Christoph Hellwig <hch@....de>
> 
> Here we go, after another round of xfstests.
> 
> The next question, since it touches vfs infrastructure, is which tree
> this patch queue should be merged through.  Al?

Discussions with Darrick before he went on vacation/honeymoon was that
up until now changes to fs/iomap.c had been going through XFS, but
since these changes didn't affect XFS, and the rest of the patch
series touches ext4 and ext4 functionality, that he was OK with
running this patch series through the ext4 tree.  I'm OK as well, so
unless Al has any objections?

				- Ted

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ