From: Eric Sandeen <sandeen@sandeen.net>
To: Eric Sandeen <sandeen@redhat.com>, xfs-oss <xfs@oss.sgi.com>
Subject: [PATCH 1/2] xfs_logprint: Don't error out after split items lose context
Date: Wed, 26 Feb 2014 19:13:25 -0600 [thread overview]
Message-ID: <530E9135.2020807@sandeen.net> (raw)
In-Reply-To: <530E8E17.1090901@redhat.com>
xfs_logprint recognizes a "left over region from split log item"
but then expects the *next* op to be a valid start to a new
item. The problem is, we can split i.e. an xfs_inode_log_format
item, skip over it, and then land on the xfs_icdinode_t
data which follows it - this doesn't have a valid log item
magic (XFS_LI_*) and we error out. This results in something
like:
xfs_logprint: unknown log operation type (494e)
Fix this by recognizing that we've skipped over an item and
lost the context we're in, so just continue skipping over
op headers until we find the next valid start to a log item.
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---
diff --git a/logprint/log_misc.c b/logprint/log_misc.c
index cf9d59d..7070fa3 100644
--- a/logprint/log_misc.c
+++ b/logprint/log_misc.c
@@ -874,7 +874,7 @@ xlog_print_record(
int bad_hdr_warn)
{
xfs_caddr_t buf, ptr;
- int read_len, skip;
+ int read_len, skip, lost_context = 0;
int ret, n, i, j, k;
if (print_no_print)
@@ -995,7 +995,10 @@ xlog_print_record(
if (xlog_print_find_tid(be32_to_cpu(op_head->oh_tid),
op_head->oh_flags & XLOG_WAS_CONT_TRANS)) {
printf(_("Left over region from split log item\n"));
+ /* Skip this leftover bit */
ptr += be32_to_cpu(op_head->oh_len);
+ /* We've lost context; don't complain if next one looks bad too */
+ lost_context = 1;
continue;
}
@@ -1050,7 +1053,7 @@ xlog_print_record(
break;
}
default: {
- if (bad_hdr_warn) {
+ if (bad_hdr_warn && !lost_context) {
fprintf(stderr,
_("%s: unknown log operation type (%x)\n"),
progname, *(unsigned short *)ptr);
@@ -1064,6 +1067,7 @@ xlog_print_record(
}
skip = 0;
ptr += be32_to_cpu(op_head->oh_len);
+ lost_context = 0;
}
} /* switch */
} /* else */
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-02-27 1:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 1:00 [PATCH 0/2] xfs_logprint: Get xfstests/xfs/295 passing w/ CRCs Eric Sandeen
2014-02-27 1:13 ` Eric Sandeen [this message]
2014-02-27 1:27 ` [PATCH 1/2] xfs_logprint: Don't error out after split items lose context Dave Chinner
2014-02-27 1:15 ` [PATCH 2/2] xfs_logprint: don't advance op counter in xlog_print_trans_icreate Eric Sandeen
2014-02-27 1:28 ` Dave Chinner
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=530E9135.2020807@sandeen.net \
--to=sandeen@sandeen.net \
--cc=sandeen@redhat.com \
--cc=xfs@oss.sgi.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