Re: [PATCH 04/14] xfs: buffered write failure should not truncate the page cache

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

Subject: Re: [PATCH 04/14] xfs: buffered write failure should not truncate the page cache
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue, 15 Nov 2022 00:32:53 -0800
Cc: Dave Chinner <dchinner@xxxxxxxxxx>, linux-xfs@xxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, david@xxxxxxxxxxxxx, hch@xxxxxxxxxxxxx
In-reply-to: <166801776726.3992140.478044755009071447.stgit@magnolia>
References: <166801774453.3992140.241667783932550826.stgit@magnolia> <166801776726.3992140.478044755009071447.stgit@magnolia>

On Wed, Nov 09, 2022 at 10:16:07AM -0800, Darrick J. Wong wrote:
>  mm/filemap.c       |    1 

These new exports are another really good indicator that the
punch out delalloc code really should live in iomap and not in
the file system.

References:
- [PATCHSET RFCRAP v2 00/14] xfs, iomap: fix data corruption due to stale cached iomaps
  - From: Darrick J. Wong
- [PATCH 04/14] xfs: buffered write failure should not truncate the page cache
  - From: Darrick J. Wong

Prev by Date: Re: [PATCH] xfs: account extra freespace btree splits for multiple allocations
Next by Date: Re: [PATCH 08/14] iomap: pass iter to ->iomap_begin implementations
Previous by thread: [PATCH 04/14] xfs: buffered write failure should not truncate the page cache
Next by thread: [PATCH 07/14] xfs: drop write error injection is unfixable, remove it
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]

Powered by Linux