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]

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>
References: <20191016051101.12620-1-david@fromorbit.com> <20191016060604.GH16973@dread.disaster.area> <20191017122911.GC25548@mit.edu> <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: [ANNOUNCE] xfsprogs for-next updated to cac2b8b0
Next by Date: Re: [PATCH 3/3] xfs: use deferred frees to reap old btree blocks
Previous by thread: Re: [PATCH v2] iomap: iomap that extends beyond EOF should be marked dirty
Next by thread: [PATCH v2] fsstress: add renameat2 support
Index(es):
- Date
- Thread

[Index of Archives] [XFS Filesystem Development (older mail)] [Linux Filesystem Development] [Linux Audio Users] [Yosemite Trails] [Linux Kernel] [Linux RAID] [Linux SCSI]