Re: [PATCH 1/2] iomap: use page dirty state to seek data over unwritten extents

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

To: Brian Foster <bfoster@xxxxxxxxxx>
Subject: Re: [PATCH 1/2] iomap: use page dirty state to seek data over unwritten extents
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Thu, 15 Oct 2020 10:47:00 +0100
Cc: linux-fsdevel@xxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxxxxxx
In-reply-to: <20201012140350.950064-2-bfoster@redhat.com>

I don't think we can solve this properly.  Due to the racyness we can
always err one side.  The beauty of treating all the uptodate pages
as present data is that we err on the safe side, as applications
expect holes to never have data, while "data" could always be zeroed.

Follow-Ups:
- Re: [PATCH 1/2] iomap: use page dirty state to seek data over unwritten extents
  - From: Brian Foster

References:
- [PATCH 0/2] iomap: zero dirty pages over unwritten extents
  - From: Brian Foster
- [PATCH 1/2] iomap: use page dirty state to seek data over unwritten extents
  - From: Brian Foster

Prev by Date: Re: [PATCH 0/4] Some more lock_page work..
Next by Date: Re: [PATCH 2/2] iomap: zero cached pages over unwritten extents on zero range
Previous by thread: Re: [PATCH 1/2] iomap: use page dirty state to seek data over unwritten extents
Next by thread: Re: [PATCH 1/2] iomap: use page dirty state to seek data over unwritten extents
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