Re: [PATCH v2 1/2] iomap: fix handling of dirty folios over unwritten extents

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

Subject: Re: [PATCH v2 1/2] iomap: fix handling of dirty folios over unwritten extents
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Wed, 28 Aug 2024 22:43:49 -0700
Cc: Brian Foster <bfoster@xxxxxxxxxx>, linux-fsdevel@xxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxxxxxx, josef@xxxxxxxxxxxxxx, david@xxxxxxxxxxxxx
In-reply-to: <20240828222222.GB6224@frogsfrogsfrogs>
References: <20240828181912.41517-1-bfoster@redhat.com> <20240828181912.41517-2-bfoster@redhat.com> <20240828222222.GB6224@frogsfrogsfrogs>

On Wed, Aug 28, 2024 at 03:22:22PM -0700, Darrick J. Wong wrote:
> I wonder why gfs2 (aka the other iomap_zero_range user) doesn't have a
> truncate-down flush hammer, but maybe it doesn't support unwritten
> extents?  I didn't find anything obvious when I looked, so

gfs2 does not support unwritten extents.

References:
- [PATCH v2 0/2] iomap: flush dirty cache over unwritten mappings on zero range
  - From: Brian Foster
- [PATCH v2 1/2] iomap: fix handling of dirty folios over unwritten extents
  - From: Brian Foster
- Re: [PATCH v2 1/2] iomap: fix handling of dirty folios over unwritten extents
  - From: Darrick J. Wong

Prev by Date: Re: [PATCH 2/2] iomap: make zero range flush conditional on unwritten mappings
Next by Date: Re: [PATCH v4 08/16] fanotify: report file range info with pre-content events
Previous by thread: Re: [PATCH v2 1/2] iomap: fix handling of dirty folios over unwritten extents
Next by thread: [PATCH v2 2/2] iomap: make zero range flush conditional on unwritten mappings
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