From: Dave Chinner <david@fromorbit.com>
To: Chandan Babu R <chandan.babu@oracle.com>
Cc: linux-xfs@vger.kernel.org, djwong@kernel.org
Subject: Re: [PATCH V3 06/12] xfs: xfs_dfork_nextents: Return extent count via an out argument
Date: Thu, 30 Sep 2021 11:19:22 +1000 [thread overview]
Message-ID: <20210930011922.GN2361455@dread.disaster.area> (raw)
In-Reply-To: <20210916100647.176018-7-chandan.babu@oracle.com>
On Thu, Sep 16, 2021 at 03:36:41PM +0530, Chandan Babu R wrote:
> This commit changes xfs_dfork_nextents() to return an error code. The extent
> count itself is now returned through an out argument. This facility will be
> used by a future commit to indicate an inconsistent ondisk extent count.
>
> Signed-off-by: Chandan Babu R <chandan.babu@oracle.com>
> ---
> fs/xfs/libxfs/xfs_format.h | 14 ++---
> fs/xfs/libxfs/xfs_inode_buf.c | 16 ++++--
> fs/xfs/libxfs/xfs_inode_fork.c | 21 ++++++--
> fs/xfs/scrub/inode.c | 94 +++++++++++++++++++++-------------
> fs/xfs/scrub/inode_repair.c | 34 ++++++++----
> 5 files changed, 118 insertions(+), 61 deletions(-)
>
> diff --git a/fs/xfs/libxfs/xfs_format.h b/fs/xfs/libxfs/xfs_format.h
> index b4638052801f..dba868f2c3e3 100644
> --- a/fs/xfs/libxfs/xfs_format.h
> +++ b/fs/xfs/libxfs/xfs_format.h
> @@ -931,28 +931,30 @@ enum xfs_dinode_fmt {
> (dip)->di_format : \
> (dip)->di_aformat)
>
> -static inline xfs_extnum_t
> +static inline int
> xfs_dfork_nextents(
> struct xfs_dinode *dip,
> - int whichfork)
> + int whichfork,
> + xfs_extnum_t *nextents)
> {
> - xfs_extnum_t nextents = 0;
> + int error = 0;
>
> switch (whichfork) {
> case XFS_DATA_FORK:
> - nextents = be32_to_cpu(dip->di_nextents);
> + *nextents = be32_to_cpu(dip->di_nextents);
> break;
>
> case XFS_ATTR_FORK:
> - nextents = be16_to_cpu(dip->di_anextents);
> + *nextents = be16_to_cpu(dip->di_anextents);
> break;
>
> default:
> ASSERT(0);
> + error = -EFSCORRUPTED;
> break;
> }
>
> - return nextents;
> + return error;
> }
So why do we need to do this? AFAICT, the only check that can return
errors that is added by the ned of the patch series is a
on-disk-format check that does:
if (inode_has_nrext64 && dip->di_nextents16 != 0)
return -EFSCORRUPTED;
This doesn't belong here - it is conflating verification with
extraction. Verfication of the on-disk format belongs in the
verifiers or verification code, not in the function that extracts
> /*
> diff --git a/fs/xfs/libxfs/xfs_inode_buf.c b/fs/xfs/libxfs/xfs_inode_buf.c
> index 176c98798aa4..dc511630cc7a 100644
> --- a/fs/xfs/libxfs/xfs_inode_buf.c
> +++ b/fs/xfs/libxfs/xfs_inode_buf.c
> @@ -345,7 +345,8 @@ xfs_dinode_verify_fork(
> xfs_extnum_t di_nextents;
> xfs_extnum_t max_extents;
>
> - di_nextents = xfs_dfork_nextents(dip, whichfork);
> + if (xfs_dfork_nextents(dip, whichfork, &di_nextents))
> + return __this_address;
>
> switch (XFS_DFORK_FORMAT(dip, whichfork)) {
> case XFS_DINODE_FMT_LOCAL:
> @@ -477,6 +478,7 @@ xfs_dinode_verify(
> uint64_t flags2;
> uint64_t di_size;
> xfs_extnum_t nextents;
> + xfs_extnum_t naextents;
> xfs_rfsblock_t nblocks;
>
> if (dip->di_magic != cpu_to_be16(XFS_DINODE_MAGIC))
> @@ -508,8 +510,13 @@ xfs_dinode_verify(
> if ((S_ISLNK(mode) || S_ISDIR(mode)) && di_size == 0)
> return __this_address;
>
> - nextents = xfs_dfork_nextents(dip, XFS_DATA_FORK);
> - nextents += xfs_dfork_nextents(dip, XFS_ATTR_FORK);
> + if (xfs_dfork_nextents(dip, XFS_DATA_FORK, &nextents))
> + return __this_address;
> +
> + if (xfs_dfork_nextents(dip, XFS_ATTR_FORK, &naextents))
> + return __this_address;
Yeah, so this should end up being:
xfs_failaddr_t
xfs_dfork_nextents_verify(
... )
{
if (ip->di_flags2 & NREXT64) {
if (!xfs_has_nrext64(mp))
return __this_address;
if (dip->di_nextents16 != 0)
return __this_address;
} else if (dip->di_nextents64 != 0)
return __this_address;
}
return NULL;
}
and
faddr = xfs_dfork_nextents_verify(dip, mp);
if (faddr)
return faddr;
nextents = xfs_dfork_nextents(dip, XFS_DATA_FORK);
naextents = xfs_dfork_nextents(dip, XFS_ATTR_FORK);
Now all the verification can be removed from xfs_dfork_nextents(),
and anything that needs to verify that the extent counts are in a
valid format can call xfs_dfork_nextents_verify() to perform this
check (i.e. the dinode verifiers and scrub checking code).
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2021-09-30 1:19 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 10:06 [PATCH V3 00/12] xfs: Extend per-inode extent counters Chandan Babu R
2021-09-16 10:06 ` [PATCH V3 01/12] xfs: Move extent count limits to xfs_format.h Chandan Babu R
2021-09-16 10:06 ` [PATCH V3 02/12] xfs: Introduce xfs_iext_max_nextents() helper Chandan Babu R
2021-09-16 10:06 ` [PATCH V3 03/12] xfs: Rename MAXEXTNUM, MAXAEXTNUM to XFS_IFORK_EXTCNT_MAXS32, XFS_IFORK_EXTCNT_MAXS16 Chandan Babu R
2021-09-16 10:06 ` [PATCH V3 04/12] xfs: Use xfs_extnum_t instead of basic data types Chandan Babu R
2021-09-16 10:06 ` [PATCH V3 05/12] xfs: Introduce xfs_dfork_nextents() helper Chandan Babu R
2021-09-27 22:46 ` Dave Chinner
2021-09-28 9:46 ` Chandan Babu R
2021-09-16 10:06 ` [PATCH V3 06/12] xfs: xfs_dfork_nextents: Return extent count via an out argument Chandan Babu R
2021-09-30 1:19 ` Dave Chinner [this message]
2021-09-16 10:06 ` [PATCH V3 07/12] xfs: Rename inode's extent counter fields based on their width Chandan Babu R
2021-09-27 23:46 ` Dave Chinner
2021-09-28 4:04 ` Dave Chinner
2021-09-29 17:03 ` Chandan Babu R
2021-09-30 0:40 ` Dave Chinner
2021-09-30 4:31 ` Dave Chinner
2021-09-30 7:30 ` Chandan Babu R
2021-09-30 22:55 ` Dave Chinner
2021-10-07 10:52 ` Chandan Babu R
2021-10-10 21:49 ` Dave Chinner
2021-10-13 14:44 ` Chandan Babu R
2021-10-14 2:00 ` Dave Chinner
2021-10-14 10:07 ` Chandan Babu R
2021-10-21 10:27 ` Chandan Babu R
2021-09-28 9:47 ` Chandan Babu R
2021-09-16 10:06 ` [PATCH V3 08/12] xfs: Promote xfs_extnum_t and xfs_aextnum_t to 64 and 32-bits respectively Chandan Babu R
2021-09-28 0:47 ` Dave Chinner
2021-09-28 9:47 ` Chandan Babu R
2021-09-28 23:08 ` Dave Chinner
2021-09-29 17:04 ` Chandan Babu R
2021-09-16 10:06 ` [PATCH V3 09/12] xfs: Enable bulkstat ioctl to support 64-bit per-inode extent counters Chandan Babu R
2021-09-27 23:06 ` Dave Chinner
2021-09-28 9:49 ` Chandan Babu R
2021-09-28 23:39 ` Dave Chinner
2021-09-29 17:04 ` Chandan Babu R
2021-09-16 10:06 ` [PATCH V3 10/12] xfs: Extend per-inode extent counter widths Chandan Babu R
2021-09-16 10:06 ` [PATCH V3 11/12] xfs: Add XFS_SB_FEAT_INCOMPAT_NREXT64 to XFS_SB_FEAT_INCOMPAT_ALL Chandan Babu R
2021-09-16 10:06 ` [PATCH V3 12/12] xfs: Define max extent length based on on-disk format definition Chandan Babu R
2021-09-28 0:33 ` Dave Chinner
2021-09-28 10:07 ` Chandan Babu R
2021-09-18 0:03 ` [PATCH V3 00/12] xfs: Extend per-inode extent counters Darrick J. Wong
2021-09-18 3:36 ` [External] : " Chandan Babu R
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=20210930011922.GN2361455@dread.disaster.area \
--to=david@fromorbit.com \
--cc=chandan.babu@oracle.com \
--cc=djwong@kernel.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;
as well as URLs for NNTP newsgroup(s).