From: Brian Foster <bfoster@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>,
linux-xfs@vger.kernel.org, hch@infradead.org
Subject: Re: [PATCH 1/3] xfs: force writes to delalloc regions to unwritten
Date: Tue, 19 May 2020 08:45:53 -0400 [thread overview]
Message-ID: <20200519124553.GA23387@bfoster> (raw)
In-Reply-To: <158984935136.619853.1558687512700172480.stgit@magnolia>
On Mon, May 18, 2020 at 05:49:11PM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <darrick.wong@oracle.com>
>
> When writing to a delalloc region in the data fork, commit the new
> allocations (of the da reservation) as unwritten so that the mappings
> are only marked written once writeback completes successfully. This
> fixes the problem of stale data exposure if the system goes down during
> targeted writeback of a specific region of a file, as tested by
> generic/042.
>
We could probably add generic/042 into the auto group once this patch
lands.
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
> ---
> fs/xfs/libxfs/xfs_bmap.c | 28 +++++++++++++++++-----------
> 1 file changed, 17 insertions(+), 11 deletions(-)
>
>
> diff --git a/fs/xfs/libxfs/xfs_bmap.c b/fs/xfs/libxfs/xfs_bmap.c
> index fda13cd7add0..825d170e1503 100644
> --- a/fs/xfs/libxfs/xfs_bmap.c
> +++ b/fs/xfs/libxfs/xfs_bmap.c
...
> @@ -4611,8 +4601,24 @@ xfs_bmapi_convert_delalloc(
> bma.offset = bma.got.br_startoff;
> bma.length = max_t(xfs_filblks_t, bma.got.br_blockcount, MAXEXTLEN);
> bma.minleft = xfs_bmapi_minleft(tp, ip, whichfork);
> +
> + /*
> + * When we're converting the delalloc reservations backing dirty pages
> + * in the page cache, we must be careful about how we create the new
> + * extents:
> + *
> + * New CoW fork extents are created unwritten, turned into real extents
> + * when we're about to write the data to disk, and mapped into the data
> + * fork after the write finishes. End of story.
> + *
> + * New data fork extents must be mapped in as unwritten and converted
> + * to real extents after the write succeeds to avoid exposing stale
> + * disk contents if we crash.
> + */
> if (whichfork == XFS_COW_FORK)
> bma.flags = XFS_BMAPI_COWFORK | XFS_BMAPI_PREALLOC;
> + else
> + bma.flags = XFS_BMAPI_PREALLOC;
The following seems a bit cleaner:
bma.flags = XFS_BMAPI_PREALLOC;
if (whichfork == XFS_COW_FORK)
bma.flags |= XFS_BMAPI_COWFORK;
... but nit aside, LGTM:
Reviewed-by: Brian Foster <bfoster@redhat.com>
>
> if (!xfs_iext_peek_prev_extent(ifp, &bma.icur, &bma.prev))
> bma.prev.br_startoff = NULLFILEOFF;
>
next prev parent reply other threads:[~2020-05-19 12:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 0:49 [PATCH 0/3] xfs: fix stale disk exposure after crash Darrick J. Wong
2020-05-19 0:49 ` [PATCH 1/3] xfs: force writes to delalloc regions to unwritten Darrick J. Wong
2020-05-19 12:45 ` Brian Foster [this message]
2020-05-19 0:49 ` [PATCH 2/3] xfs: don't fail unwritten extent conversion on writeback due to edquot Darrick J. Wong
2020-05-19 7:13 ` Christoph Hellwig
2020-05-19 12:46 ` Brian Foster
2020-05-19 0:49 ` [PATCH 3/3] xfs: measure all contiguous previous extents for prealloc size Darrick J. Wong
2020-05-19 12:48 ` Brian Foster
2020-05-20 13:23 ` Brian Foster
2020-05-20 19:48 ` Darrick J. Wong
2020-05-21 12:24 ` Brian Foster
2020-05-19 12:54 ` Christoph Hellwig
2020-05-20 21:17 ` Darrick J. Wong
2020-05-21 9:31 ` Christoph Hellwig
2020-05-21 17:19 ` Darrick J. Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200519124553.GA23387@bfoster \
--to=bfoster@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=linux-xfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).