Re: [PATCH 01/14] iomap: iomap that extends beyond EOF should be marked dirty

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
Subject: Re: [PATCH 01/14] iomap: iomap that extends beyond EOF should be marked dirty
From: Christoph Hellwig <hch@xxxxxx>
Date: Fri, 18 Oct 2019 09:20:40 +0200
Cc: Christoph Hellwig <hch@xxxxxx>, Damien Le Moal <Damien.LeMoal@xxxxxxx>, Andreas Gruenbacher <agruenba@xxxxxxxxxx>, linux-xfs@xxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, Dave Chinner <dchinner@xxxxxxxxxx>
In-reply-to: <20191017183917.GL13108@magnolia>
User-agent: Mutt/1.5.17 (2007-11-01)

On Thu, Oct 17, 2019 at 11:39:17AM -0700, Darrick J. Wong wrote:
> Looks ok, but need fixes tag.  Also, might it be wise to split off the
> ext4 section into a separate patch so that it can be backported
> separately?

I'll let Dave handle all that.  I've just pulled it in here as multiple
patches conflict with this one.

References:
- lift the xfs writepage code into iomap v8
  - From: Christoph Hellwig
- [PATCH 01/14] iomap: iomap that extends beyond EOF should be marked dirty
  - From: Christoph Hellwig
- Re: [PATCH 01/14] iomap: iomap that extends beyond EOF should be marked dirty
  - From: Darrick J. Wong

Prev by Date: Re: [PATCH] iomap: enhance writeback error message
Next by Date: [PATCH] f*xattr: allow O_PATH descriptors
Previous by thread: Re: [PATCH 01/14] iomap: iomap that extends beyond EOF should be marked dirty
Next by thread: [PATCH 03/14] xfs: set IOMAP_F_NEW more carefully
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [Samba] [Device Mapper] [CEPH Development]

Powered by Linux