From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: linux-xfs@vger.kernel.org, sandeen@redhat.com
Subject: Re: xfs_db and ASSERT fails dur type mismatch
Date: Wed, 9 May 2018 09:27:10 -0700 [thread overview]
Message-ID: <20180509162710.GU11261@magnolia> (raw)
In-Reply-To: <20180509114554.2slvfi3hqt4na6vy@odin.usersys.redhat.com>
On Wed, May 09, 2018 at 01:45:54PM +0200, Carlos Maiolino wrote:
> Hey folks,
>
> I've been thinking about different ways to fix those crashes on xfs_db due type
> mismatch, based on the previous discussion and a chat I had with Eric on irc.
>
> After thinking a bit more about it, I do think using unknown header types adds
> unneeded extra complexity to the code, to achieve the same result as an extra
> check on print_flist_1().
>
> Adding an unknown type, will require a change to all types affected by this
> issue. I am not sure if a single unknown type can be used for all metadata types
> which is affected by this, but I think it requires an unknown type for each of
> these metadata. Or at least an entry for an unknown header type (in case of of
> the known ones are not found).
>
> While, the crash caused by unrecognized metadata when using these types, can be
> fixed by something like my original change.
>
> I wrote a slightly different patch like this:
>
> diff --git a/db/print.c b/db/print.c
> index 0da36c27..f8a48281 100644
> --- a/db/print.c
> +++ b/db/print.c
> @@ -160,9 +160,10 @@ print_flist_1(
> (f->flags & FLD_ARRAY) != 0);
> if (neednl)
> dbprintf("\n");
> - } else {
> - ASSERT(fa->arg & FTARG_OKEMPTY);
> + } else if (fa->arg & FTARG_OKEMPTY) {
> dbprintf(_("(empty)\n"));
> + } else {
> + dbprintf(_("Unrecognized metadata or type mismatch\n"));
> }
> }
> free_strvec(pfx);
>
>
> This will still keep printing "(empty)" where it should be printed, or print out
> a hint that something went wrong.
>
> I honestly think this the best solution for these crashes, what you guys think?
Looks fine to me, I dislike ASSERTs on crap metadata, especially in the
debugging tool.
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
--D
>
> Cheers
>
>
> --
> Carlos
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-05-09 16:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 11:45 xfs_db and ASSERT fails dur type mismatch Carlos Maiolino
2018-05-09 16:27 ` Darrick J. Wong [this message]
2018-05-31 16:24 ` 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=20180509162710.GU11261@magnolia \
--to=darrick.wong@oracle.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@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).