From: "Darrick J. Wong" <djwong@kernel.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Christoph Hellwig <hch@lst.de>,
Chandan Babu R <chandan.babu@oracle.com>,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH 4/6] xfs: simplify iext overflow checking and upgrade
Date: Fri, 29 Mar 2024 09:24:29 -0700 [thread overview]
Message-ID: <20240329162429.GH6390@frogsfrogsfrogs> (raw)
In-Reply-To: <ZgXpewa/XiT7w4wY@dread.disaster.area>
On Fri, Mar 29, 2024 at 09:04:43AM +1100, Dave Chinner wrote:
> On Thu, Mar 28, 2024 at 08:02:54AM +0100, Christoph Hellwig wrote:
> > Currently the calls to xfs_iext_count_may_overflow and
> > xfs_iext_count_upgrade are always paired. Merge them into a single
> > function to simplify the callers and the actual check and upgrade
> > logic itself.
> >
> > Signed-off-by: Christoph Hellwig <hch@lst.de>
> > ---
> > fs/xfs/libxfs/xfs_attr.c | 5 +--
> > fs/xfs/libxfs/xfs_bmap.c | 5 +--
> > fs/xfs/libxfs/xfs_inode_fork.c | 62 ++++++++++++++++------------------
> > fs/xfs/libxfs/xfs_inode_fork.h | 4 +--
> > fs/xfs/xfs_bmap_item.c | 4 +--
> > fs/xfs/xfs_bmap_util.c | 24 +++----------
> > fs/xfs/xfs_dquot.c | 5 +--
> > fs/xfs/xfs_iomap.c | 9 ++---
> > fs/xfs/xfs_reflink.c | 9 ++---
> > fs/xfs/xfs_rtalloc.c | 5 +--
> > 10 files changed, 44 insertions(+), 88 deletions(-)
>
> ....
>
> > diff --git a/fs/xfs/libxfs/xfs_inode_fork.c b/fs/xfs/libxfs/xfs_inode_fork.c
> > index 7d660a9739090a..235c41eca5edd7 100644
> > --- a/fs/xfs/libxfs/xfs_inode_fork.c
> > +++ b/fs/xfs/libxfs/xfs_inode_fork.c
> > @@ -765,53 +765,49 @@ xfs_ifork_verify_local_attr(
> > return 0;
> > }
> >
> > +/*
> > + * Check if the inode fork supports adding nr_to_add more extents.
> > + *
> > + * If it doesn't but we can upgrade it to large extent counters, do the upgrade.
> > + * If we can't upgrade or are already using big counters but still can't fit the
> > + * additional extents, return -EFBIG.
> > + */
> > int
> > -xfs_iext_count_may_overflow(
> > +xfs_iext_count_upgrade(
> > + struct xfs_trans *tp,
> > struct xfs_inode *ip,
> > int whichfork,
> > - int nr_to_add)
> > + uint nr_to_add)
> > {
> > + struct xfs_mount *mp = ip->i_mount;
> > + bool has_large =
> > + xfs_inode_has_large_extent_counts(ip);
> > struct xfs_ifork *ifp = xfs_ifork_ptr(ip, whichfork);
> > uint64_t max_exts;
> > uint64_t nr_exts;
> >
> > + ASSERT(nr_to_add <= XFS_MAX_EXTCNT_UPGRADE_NR);
> > +
> > if (whichfork == XFS_COW_FORK)
> > return 0;
> >
> > - max_exts = xfs_iext_max_nextents(xfs_inode_has_large_extent_counts(ip),
> > - whichfork);
> > -
> > - if (XFS_TEST_ERROR(false, ip->i_mount, XFS_ERRTAG_REDUCE_MAX_IEXTENTS))
> > - max_exts = 10;
> > -
> > nr_exts = ifp->if_nextents + nr_to_add;
> > - if (nr_exts < ifp->if_nextents || nr_exts > max_exts)
> > + if (nr_exts < ifp->if_nextents) {
> > + /* no point in upgrading if if_nextents overflows */
> > return -EFBIG;
> > + }
> >
> > - return 0;
> > -}
> > -
> > -/*
> > - * Upgrade this inode's extent counter fields to be able to handle a potential
> > - * increase in the extent count by nr_to_add. Normally this is the same
> > - * quantity that caused xfs_iext_count_may_overflow() to return -EFBIG.
> > - */
> > -int
> > -xfs_iext_count_upgrade(
> > - struct xfs_trans *tp,
> > - struct xfs_inode *ip,
> > - uint nr_to_add)
> > -{
> > - ASSERT(nr_to_add <= XFS_MAX_EXTCNT_UPGRADE_NR);
> > -
> > - if (!xfs_has_large_extent_counts(ip->i_mount) ||
> > - xfs_inode_has_large_extent_counts(ip) ||
> > - XFS_TEST_ERROR(false, ip->i_mount, XFS_ERRTAG_REDUCE_MAX_IEXTENTS))
> > - return -EFBIG;
> > -
> > - ip->i_diflags2 |= XFS_DIFLAG2_NREXT64;
> > - xfs_trans_log_inode(tp, ip, XFS_ILOG_CORE);
> > -
> > + if (XFS_TEST_ERROR(false, mp, XFS_ERRTAG_REDUCE_MAX_IEXTENTS))
> > + max_exts = 10;
> > + else
> > + max_exts = xfs_iext_max_nextents(has_large, whichfork);
> > + if (nr_exts > max_exts) {
> > + if (has_large || !xfs_has_large_extent_counts(mp) ||
> > + XFS_TEST_ERROR(false, mp, XFS_ERRTAG_REDUCE_MAX_IEXTENTS))
> > + return -EFBIG;
> > + ip->i_diflags2 |= XFS_DIFLAG2_NREXT64;
> > + xfs_trans_log_inode(tp, ip, XFS_ILOG_CORE);
> > + }
>
> IIUC, testing the error tag twice won't always give the same result.
> I think this will be more reliable, and it self-documents the error
> injection case better:
>
> if (XFS_TEST_ERROR(false, ip->i_mount, XFS_ERRTAG_REDUCE_MAX_IEXTENTS) &&
> nr_exts > 10))
> return -EFBIG;
>
> if (nr_exts > xfs_iext_max_nextents(has_large, whichfork)) {
> if (has_large || !xfs_has_large_extent_counts(mp))
> return -EFBIG;
> ip->i_diflags2 |= XFS_DIFLAG2_NREXT64;
> xfs_trans_log_inode(tp, ip, XFS_ILOG_CORE);
> }
> return 0;
Agreed, that looks better to me than sampling the errtag twice.
--D
> -Dave.
> --
> Dave Chinner
> david@fromorbit.com
>
next prev parent reply other threads:[~2024-03-29 16:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 7:02 RFC: optimize COW end I/O remapping Christoph Hellwig
2024-03-28 7:02 ` [PATCH 1/6] xfs: check if_bytes under the ilock in xfs_reflink_end_cow_extent Christoph Hellwig
2024-03-29 16:14 ` Darrick J. Wong
2024-03-30 5:56 ` Christoph Hellwig
2024-03-28 7:02 ` [PATCH 2/6] xfs: consolidate the xfs_quota_reserve_blkres defintions Christoph Hellwig
2024-03-29 16:16 ` Darrick J. Wong
2024-03-28 7:02 ` [PATCH 3/6] xfs: xfs_quota_unreserve_blkres can't fail Christoph Hellwig
2024-03-29 16:21 ` Darrick J. Wong
2024-03-30 5:57 ` Christoph Hellwig
2024-04-02 1:41 ` Darrick J. Wong
2024-03-28 7:02 ` [PATCH 4/6] xfs: simplify iext overflow checking and upgrade Christoph Hellwig
2024-03-28 22:04 ` Dave Chinner
2024-03-29 4:10 ` Christoph Hellwig
2024-03-29 16:24 ` Darrick J. Wong [this message]
2024-03-28 7:02 ` [PATCH 5/6] xfs: optimize extent remapping in xfs_reflink_end_cow_extent Christoph Hellwig
2024-03-29 16:29 ` Darrick J. Wong
2024-03-30 6:00 ` Christoph Hellwig
2024-03-28 7:02 ` [PATCH 6/6] xfs: rename the del variable " Christoph Hellwig
2024-03-29 16:31 ` Darrick J. Wong
2024-03-30 5:59 ` 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=20240329162429.GH6390@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=chandan.babu@oracle.com \
--cc=david@fromorbit.com \
--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