From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Dave Chinner <david@fromorbit.com>,
Eric Sandeen <sandeen@redhat.com>,
xfs <linux-xfs@vger.kernel.org>,
zlang@redhat.com
Subject: Re: [PATCH] xfs: zero posteof blocks when cloning above eof
Date: Wed, 3 Oct 2018 08:12:53 -0700 [thread overview]
Message-ID: <20181003151253.GF19324@magnolia> (raw)
In-Reply-To: <24443553-fc5e-a377-dcb4-dabc0177bf99@sandeen.net>
On Wed, Oct 03, 2018 at 07:11:14AM -0500, Eric Sandeen wrote:
> On 10/2/18 9:03 PM, Darrick J. Wong wrote:
> > From: Darrick J. Wong <darrick.wong@oracle.com>
> >
> > When we're reflinking between two files and the destination file range
> > is well beyond the destination file's EOF marker, zero any posteof
> > speculative preallocations in the destination file so that we don't
> > expose stale disk contents. The previous strategy of trying to clear
> > the preallocations does not work if the destination file has the
> > PREALLOC flag set but no delalloc blocks.
> >
> > Uncovered by shared/010.
> >
> > Reported-by: Zorro Lang <zlang@redhat.com>
> > Bugzilla-id: https://bugzilla.kernel.org/show_bug.cgi?id=201259
> > Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
>
> The action makes sense, and this does resolve my simple testcase,
> and makes shared/010 pass for me as well.
>
> However, this makes my correctness spidey-sense tingle; why is there a
> new helper unique to extending reflinks, when extending writes already
> must do the same thing?
I think you're referring to Dave's earlier question of "Why don't you
just use xfs_file_aio_write_checks?"
It's tempting to adapt xfs_file_aio_write_checks for reflink, but I
think I have to create a new function because (a) we don't have a kiocb
to pass in, and (b) we have to lock two inodes for reflink while abiding
the [VX]FS inode locking rules and making sure we break the destination
flie's layout correctly.
> I didn't follow all the discussion on IRC, but might be worth
> explaining on the list for others as well. Are there any other
> extending write tests that aren't happening for extending reflink?
Yes, there are a number of behavioral inconsistencies between regular
write and clonerange that have been discovered in the past few days, and
it's going to take me a few days to clean all of this up:
- Lack of file_update_times(), though the ctime update is open-coded in
the reflink routines.
- Lack of file_remove_privs() to drop suid and capabilities on write.
Totally missing from the btrfs implementation and xfs/ocfs2 followed
that behavior warts and all.
- Lack of RLIMIT_FSIZE checking: D'oh. Same lame excuse as above.
- Lack of MAX_NON_LFS size checking: Same.
- Lack of s_maxbytes checking: Same. Alarming since this means we can
reflink to offsets the pagecache doesn't support.
- Should our clonerange return bytes reflinked to copy_file_range?
That last one requires more careful consideration & will take longer;
the first two are nearly ready.
--D
> -Eric
>
> > ---
> > fs/xfs/xfs_reflink.c | 34 ++++++++++++++++++++++++++--------
> > 1 file changed, 26 insertions(+), 8 deletions(-)
> >
> > diff --git a/fs/xfs/xfs_reflink.c b/fs/xfs/xfs_reflink.c
> > index 38f405415b88..c8e996a99a74 100644
> > --- a/fs/xfs/xfs_reflink.c
> > +++ b/fs/xfs/xfs_reflink.c
> > @@ -1195,6 +1195,27 @@ xfs_iolock_two_inodes_and_break_layout(
> > return 0;
> > }
> >
> > +/*
> > + * If we're reflinking to a point past the destination file's EOF, we must
> > + * zero any speculative post-EOF preallocations that sit between the old EOF
> > + * and the destination file offset.
> > + */
> > +static int
> > +xfs_reflink_zero_posteof(
> > + struct xfs_inode *ip,
> > + loff_t pos)
> > +{
> > + loff_t isize = i_size_read(VFS_I(ip));
> > + bool did_zeroing = false;
> > +
> > + if (pos <= isize)
> > + return 0;
> > +
> > + trace_xfs_zero_eof(ip, isize, pos - isize);
> > + return iomap_zero_range(VFS_I(ip), isize, pos - isize, &did_zeroing,
> > + &xfs_iomap_ops);
> > +}
> > +
> > /*
> > * Link a range of blocks from one file to another.
> > */
> > @@ -1257,15 +1278,12 @@ xfs_reflink_remap_range(
> > trace_xfs_reflink_remap_range(src, pos_in, len, dest, pos_out);
> >
> > /*
> > - * Clear out post-eof preallocations because we don't have page cache
> > - * backing the delayed allocations and they'll never get freed on
> > - * their own.
> > + * Zero existing post-eof speculative preallocations in the destination
> > + * file.
> > */
> > - if (xfs_can_free_eofblocks(dest, true)) {
> > - ret = xfs_free_eofblocks(dest);
> > - if (ret)
> > - goto out_unlock;
> > - }
> > + ret = xfs_reflink_zero_posteof(dest, pos_out);
> > + if (ret)
> > + goto out_unlock;
> >
> > /* Set flags and remap blocks. */
> > ret = xfs_reflink_set_inode_flag(src, dest);
> >
next prev parent reply other threads:[~2018-10-03 22:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 2:03 [PATCH] xfs: zero posteof blocks when cloning above eof Darrick J. Wong
2018-10-03 12:11 ` Eric Sandeen
2018-10-03 15:12 ` Darrick J. Wong [this message]
2018-10-03 15:35 ` Eric Sandeen
2018-10-03 15:51 ` Darrick J. Wong
2018-10-03 12:20 ` Brian Foster
2018-10-03 15:18 ` 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=20181003151253.GF19324@magnolia \
--to=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=sandeen@sandeen.net \
--cc=zlang@redhat.com \
/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).