From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 2/3] xfs: truncate should remove all blocks, not just to the end of the page cache
Date: Wed, 8 Jan 2020 08:37:27 -0800 [thread overview]
Message-ID: <20200108163727.GG5552@magnolia> (raw)
In-Reply-To: <20200108081157.GB25201@infradead.org>
On Wed, Jan 08, 2020 at 12:11:57AM -0800, Christoph Hellwig wrote:
> On Tue, Jan 07, 2020 at 08:17:45PM -0800, Darrick J. Wong wrote:
> > From: Darrick J. Wong <darrick.wong@oracle.com>
> >
> > xfs_itruncate_extents_flags() is supposed to unmap every block in a file
> > from EOF onwards. Oddly, it uses s_maxbytes as the upper limit to the
> > bunmapi range, even though s_maxbytes reflects the highest offset the
> > pagecache can support, not the highest offset that XFS supports.
> >
> > The result of this confusion is that if you create a 20T file on a
> > 64-bit machine, mount the filesystem on a 32-bit machine, and remove the
> > file, we leak everything above 16T. Fix this by capping the bunmapi
> > request at the maximum possible block offset, not s_maxbytes.
> >
> > Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> > ---
> > fs/xfs/xfs_inode.c | 23 +++++++++++------------
> > 1 file changed, 11 insertions(+), 12 deletions(-)
> >
> >
> > diff --git a/fs/xfs/xfs_inode.c b/fs/xfs/xfs_inode.c
> > index fc3aec26ef87..79799ab30c93 100644
> > --- a/fs/xfs/xfs_inode.c
> > +++ b/fs/xfs/xfs_inode.c
> > @@ -1518,7 +1518,6 @@ xfs_itruncate_extents_flags(
> > struct xfs_mount *mp = ip->i_mount;
> > struct xfs_trans *tp = *tpp;
> > xfs_fileoff_t first_unmap_block;
> > - xfs_fileoff_t last_block;
> > xfs_filblks_t unmap_len;
> > int error = 0;
> >
> > @@ -1540,21 +1539,21 @@ xfs_itruncate_extents_flags(
> > * the end of the file (in a crash where the space is allocated
> > * but the inode size is not yet updated), simply remove any
> > * blocks which show up between the new EOF and the maximum
> > - * possible file size. If the first block to be removed is
> > - * beyond the maximum file size (ie it is the same as last_block),
> > - * then there is nothing to do.
> > + * possible file size.
> > + *
> > + * We have to free all the blocks to the bmbt maximum offset, even if
> > + * the page cache can't scale that far.
> > */
> > first_unmap_block = XFS_B_TO_FSB(mp, (xfs_ufsize_t)new_size);
> > - last_block = XFS_B_TO_FSB(mp, mp->m_super->s_maxbytes);
> > - if (first_unmap_block == last_block)
> > + if (first_unmap_block == XFS_MAX_FILEOFF)
> > return 0;
> >
> > - ASSERT(first_unmap_block < last_block);
> > - unmap_len = last_block - first_unmap_block + 1;
> > - while (!done) {
> > + ASSERT(first_unmap_block < XFS_MAX_FILEOFF);
>
> Instead of the assert we could just do the early return for
>
> first_unmap_block >= XFS_MAX_FILEOFF
>
> and throw in a WARN_ON_ONCE, as that condition really should be nothing
> but a sanity check.
>
> Otherwise this looks good to me.
Ok, done.
--D
next prev parent reply other threads:[~2020-01-08 16:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 4:17 [PATCH v2 0/3] xfs: fix maxbytes problems on 32-bit systems Darrick J. Wong
2020-01-08 4:17 ` [PATCH 1/3] xfs: introduce XFS_MAX_FILEOFF Darrick J. Wong
2020-01-08 8:09 ` Christoph Hellwig
2020-01-08 16:37 ` Darrick J. Wong
2020-01-08 20:40 ` Dave Chinner
2020-01-08 22:32 ` Darrick J. Wong
2020-01-08 22:42 ` Dave Chinner
2020-01-08 23:04 ` Darrick J. Wong
2020-01-08 4:17 ` [PATCH 2/3] xfs: truncate should remove all blocks, not just to the end of the page cache Darrick J. Wong
2020-01-08 8:11 ` Christoph Hellwig
2020-01-08 16:37 ` Darrick J. Wong [this message]
2020-01-08 4:17 ` [PATCH 3/3] xfs: fix s_maxbytes computation on 32-bit kernels Darrick J. Wong
2020-01-08 8:12 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2020-01-09 18:44 [PATCH v3 0/3] xfs: fix maxbytes problems on 32-bit systems Darrick J. Wong
2020-01-09 18:44 ` [PATCH 2/3] xfs: truncate should remove all blocks, not just to the end of the page cache Darrick J. Wong
2020-01-10 11:52 ` Christoph Hellwig
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=20200108163727.GG5552@magnolia \
--to=darrick.wong@oracle.com \
--cc=hch@infradead.org \
--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