From: Eric Sandeen <sandeen@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 12/10] xfs_repair: use libxfs extsize/cowextsize validation helpers
Date: Wed, 25 Jul 2018 18:44:33 -0700 [thread overview]
Message-ID: <6c0bc803-dd19-2b1f-a843-b5c555fab25a@redhat.com> (raw)
In-Reply-To: <20180628173008.GJ5711@magnolia>
On 6/28/18 10:30 AM, Darrick J. Wong wrote:
> From: Darrick J. Wong <darrick.wong@oracle.com>
>
> Now that we've ported the extent size hint verifiers to libxfs, call
> them from xfs_repair instead of open-coding the checks. Tweak the
> repair message slightly to reflect the fact that we zero the field and
> clear the inode flag if the hint is garbage or is inconsistent with the
> inode flags.
>
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> ---
> libxfs/libxfs_api_defs.h | 2 +
> repair/dinode.c | 75 ++++++++++++++++------------------------------
> 2 files changed, 28 insertions(+), 49 deletions(-)
>
> diff --git a/libxfs/libxfs_api_defs.h b/libxfs/libxfs_api_defs.h
> index e5cf1554..fe8336ab 100644
> --- a/libxfs/libxfs_api_defs.h
> +++ b/libxfs/libxfs_api_defs.h
> @@ -98,6 +98,8 @@
> #define xfs_dinode_calc_crc libxfs_dinode_calc_crc
> #define xfs_idata_realloc libxfs_idata_realloc
> #define xfs_idestroy_fork libxfs_idestroy_fork
> +#define xfs_inode_validate_extsize libxfs_inode_validate_extsize
> +#define xfs_inode_validate_cowextsize libxfs_inode_validate_cowextsize
oh hey, I stepped on this with my later patches didn't I, sorry. I'll sort it out.
>
> #define xfs_rmap_ag_owner libxfs_rmap_ag_owner
> #define xfs_rmap_alloc libxfs_rmap_alloc
> diff --git a/repair/dinode.c b/repair/dinode.c
> index 4118db7c..14c055bd 100644
> --- a/repair/dinode.c
> +++ b/repair/dinode.c
> @@ -2853,24 +2853,21 @@ _("bad (negative) size %" PRId64 " on inode %" PRIu64 "\n"),
> * only regular files with REALTIME or EXTSIZE flags set can have
> * extsize set, or directories with EXTSZINHERIT.
> */
> - if (be32_to_cpu(dino->di_extsize) != 0) {
> - if ((type == XR_INO_RTDATA) ||
> - (type == XR_INO_DIR && (be16_to_cpu(dino->di_flags) &
> - XFS_DIFLAG_EXTSZINHERIT)) ||
> - (type == XR_INO_DATA && (be16_to_cpu(dino->di_flags) &
> - XFS_DIFLAG_EXTSIZE))) {
> - /* s'okay */ ;
> - } else {
> - do_warn(
> -_("bad non-zero extent size %u for non-realtime/extsize inode %" PRIu64 ", "),
> - be32_to_cpu(dino->di_extsize), lino);
> - if (!no_modify) {
> - do_warn(_("resetting to zero\n"));
> - dino->di_extsize = 0;
> - *dirty = 1;
> - } else
> - do_warn(_("would reset to zero\n"));
> - }
> + if (libxfs_inode_validate_extsize(mp,
> + be32_to_cpu(dino->di_extsize),
> + be16_to_cpu(dino->di_mode),
> + be16_to_cpu(dino->di_flags)) != NULL) {
> + do_warn(
> +_("Bad extent size %u for non-realtime/extsize inode %" PRIu64 ", "),
> + be32_to_cpu(dino->di_extsize), lino);
Failure doesn't mean it's "non-realtime/extsize" right? It could
in fact be flagged as extsize but with a bad value?
> + if (!no_modify) {
> + do_warn(_("resetting to zero\n"));
> + dino->di_extsize = 0;
> + dino->di_flags &= ~cpu_to_be16(XFS_DIFLAG_EXTSIZE |
> + XFS_DIFLAG_EXTSZINHERIT);
> + *dirty = 1;
> + } else
> + do_warn(_("would reset to zero\n"));
...
> -_("Cannot have CoW extent size of zero on cowextsize inode %" PRIu64 ", "),
> - lino);
> +_("Bad CoW extent size %u on non-cowextsize inode %" PRIu64 ", "),
> + be32_to_cpu(dino->di_cowextsize), lino);
Ditto ...
The test could also fail for a cowextsize inode if the size is not
legit, right? I'm not sure why this says "non-cowextsize inode."
So maybe just:
+_("Bad extent size %u for inode %" PRIu64 ", "),
+_("Bad CoW extent size %u on inode %" PRIu64 ", "),
? Unless you really want to keep track of "is it flagged?" and print a
different message based on flagged-or-not?
-Eric
next prev parent reply other threads:[~2018-07-26 2:59 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 2:47 [PATCH 00/10] xfsprogs-4.18: mostly scrub/repair stuff Darrick J. Wong
2018-06-27 2:47 ` [PATCH 01/10] libxfs: remove crc32 functions Darrick J. Wong
2018-06-27 2:47 ` [PATCH 02/10] libfrog: move crc32c code out of libxfs Darrick J. Wong
2018-06-27 2:48 ` [PATCH 03/10] xfs_scrub: destroy workqueues when erroring out Darrick J. Wong
2018-07-26 0:29 ` Eric Sandeen
2018-06-27 2:48 ` [PATCH 04/10] xfs_scrub: schedule and manage optimizations/repairs to the filesystem Darrick J. Wong
2018-07-26 1:06 ` Eric Sandeen
2018-07-26 1:17 ` Darrick J. Wong
2018-06-27 2:48 ` [PATCH 05/10] xfs_scrub: allow developers to force repairs Darrick J. Wong
2018-07-26 1:07 ` Eric Sandeen
2018-06-27 2:48 ` [PATCH 06/10] xfs_scrub: don't error out if an optimize-only repair isn't supported Darrick J. Wong
2018-07-26 1:09 ` Eric Sandeen
2018-06-27 2:48 ` [PATCH 07/10] xfs_scrub: rename NOFIX_COMPLAIN to be less confusing Darrick J. Wong
2018-07-26 1:10 ` Eric Sandeen
2018-06-27 2:48 ` [PATCH 08/10] xfs_scrub: only retry non-permanent repair failures Darrick J. Wong
2018-07-26 1:16 ` Eric Sandeen
2018-07-26 1:19 ` Darrick J. Wong
2018-06-27 2:48 ` [PATCH 09/10] xfs_io: wire up repair ioctl stuff Darrick J. Wong
2018-07-26 1:23 ` Eric Sandeen
2018-06-27 2:48 ` [PATCH 10/10] xfs_repair: use libxfs extsize/cowextsize validation helpers Darrick J. Wong
2018-06-27 3:25 ` Eric Sandeen
2018-06-28 17:28 ` Darrick J. Wong
2018-06-28 17:29 ` [PATCH 11/10] xfs_repair: clear extent size hints when clearing inode core Darrick J. Wong
2018-06-28 19:24 ` Eric Sandeen
2018-06-28 17:30 ` [PATCH 12/10] xfs_repair: use libxfs extsize/cowextsize validation helpers Darrick J. Wong
2018-07-26 1:44 ` Eric Sandeen [this message]
2018-07-26 1:48 ` Eric Sandeen
2018-07-26 20:38 ` [PATCH v2 " Darrick J. Wong
2018-07-27 22:44 ` Eric Sandeen
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=6c0bc803-dd19-2b1f-a843-b5c555fab25a@redhat.com \
--to=sandeen@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).