Re: [PATCH v2] iomap: iomap that extends beyond EOF should be marked dirty

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

To: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Subject: Re: [PATCH v2] iomap: iomap that extends beyond EOF should be marked dirty
From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
Date: Thu, 17 Oct 2019 10:48:08 -0400
Cc: Dave Chinner <david@xxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxxxxxx, linux-ext4@xxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, Matthew Bobrowski <mbobrowski@xxxxxxxxxxxxxx>
In-reply-to: <20191017141705.GA31558@infradead.org>
User-agent: Mutt/1.10.1 (2018-07-13)

On Thu, Oct 17, 2019 at 07:17:05AM -0700, Christoph Hellwig wrote:
> > 
> > Ext4 is not currently using iomap for any kind of writing right now,
> > so perhaps this should land via Matthew's patchset?
> 
> It does for DAX, which is one of the consumers of IOMAP_F_DIRTY.

Ah, right, I had forgotten about DAX.

					- Ted

References:
- [PATCH] iomap: iomap that extends beyond EOF should be marked dirty
  - From: Dave Chinner
- [PATCH v2] iomap: iomap that extends beyond EOF should be marked dirty
  - From: Dave Chinner
- Re: [PATCH v2] iomap: iomap that extends beyond EOF should be marked dirty
  - From: Theodore Y. Ts'o
- Re: [PATCH v2] iomap: iomap that extends beyond EOF should be marked dirty
  - From: Christoph Hellwig

Prev by Date: Re: [Y2038] [PATCH v6 10/43] compat_ioctl: move rtc handling into rtc-dev.c
Next by Date: A bug in fuse/cuse causing crashes
Previous by thread: Re: [PATCH v2] iomap: iomap that extends beyond EOF should be marked dirty
Next by thread: [RFC 0/5] Ext4: Add support for blocksize < pagesize for dioread_nolock
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]