From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 6/6] xfs: allow CoW remap transactions to use reserve blocks
Date: Thu, 14 Dec 2017 08:40:35 -0800 [thread overview]
Message-ID: <20171214164035.GF32616@infradead.org> (raw)
In-Reply-To: <151295861910.30614.17925324546800268919.stgit@magnolia>
On Sun, Dec 10, 2017 at 06:16:59PM -0800, Darrick J. Wong wrote:
> From: Darrick J. Wong <darrick.wong@oracle.com>
>
> Since we as yet have no way of holding on to the indlen blocks that are
> reserved as part of CoW fork delalloc reservations, let the CoW remap
> transaction dip into the reserves so that we avoid failing writes.
>
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Looks good,
Reviewed-by: Christoph Hellwig <hch@lst.de>
prev parent reply other threads:[~2017-12-14 16:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 2:16 [PATCH 0/6] xfs: reflink fixes Darrick J. Wong
2017-12-11 2:16 ` [PATCH 1/6] xfs: account for null transactions in bunmapi Darrick J. Wong
2017-12-14 16:37 ` Christoph Hellwig
2017-12-11 2:16 ` [PATCH 2/6] xfs: move xfs_iext_insert tracepoint to report useful information Darrick J. Wong
2017-12-14 16:37 ` Christoph Hellwig
2017-12-11 2:16 ` [PATCH 3/6] xfs: remove dest file's post-eof preallocations before reflinking Darrick J. Wong
2017-12-14 16:37 ` Christoph Hellwig
2017-12-11 2:16 ` [PATCH 4/6] xfs: relax is_reflink_inode assert in xfs_reflink_find_cow_mapping Darrick J. Wong
2017-12-14 16:38 ` Christoph Hellwig
2017-12-11 2:16 ` [PATCH 5/6] xfs: avoid infinite loop when cancelling CoW blocks after writeback failure Darrick J. Wong
2017-12-14 16:40 ` Christoph Hellwig
2017-12-11 2:16 ` [PATCH 6/6] xfs: allow CoW remap transactions to use reserve blocks Darrick J. Wong
2017-12-14 16:40 ` Christoph Hellwig [this message]
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=20171214164035.GF32616@infradead.org \
--to=hch@infradead.org \
--cc=darrick.wong@oracle.com \
--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