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

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

To: Dave Chinner <david@xxxxxxxxxxxxx>
Subject: Re: [PATCH 5/9] xfs: buffered write failure should not truncate the page cache
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue, 15 Nov 2022 00:43:43 -0800
Cc: linux-xfs@xxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx
In-reply-to: <20221115013043.360610-6-david@fromorbit.com>
References: <20221115013043.360610-1-david@fromorbit.com> <20221115013043.360610-6-david@fromorbit.com>

> +static int
> +xfs_buffered_write_delalloc_scan(

As pointed out last time, this is generic iomap (or in fact filemap.c,
but maybe start small) logic, so move it there and just pass
xfs_buffered_write_delalloc_punch as a callback.

References:
- [PATCH v2 0/9] xfs, iomap: fix data corrupton due to stale cached iomaps
  - From: Dave Chinner
- [PATCH 5/9] xfs: buffered write failure should not truncate the page cache
  - From: Dave Chinner

Prev by Date: Re: [PATCH 4/9] xfs: use byte ranges for write cleanup ranges
Next by Date: Re: [PATCH 6/9] xfs: xfs_bmap_punch_delalloc_range() should take a byte range
Previous by thread: [PATCH 5/9] xfs: buffered write failure should not truncate the page cache
Next by thread: Re: [PATCH 5/9] xfs: buffered write failure should not truncate the page cache
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Bugtraq] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API]

Powered by Linux