From: Hou Tao <houtao1@huawei.com>
To: linux-xfs@vger.kernel.org
Cc: sandeen@sandeen.net
Subject: [PATCH] xfs_logprint: handle the log split of inode item correctly
Date: Wed, 11 Jan 2017 21:38:58 +0800 [thread overview]
Message-ID: <1484141938-4195-1-git-send-email-houtao1@huawei.com> (raw)
It is possible that the data fork or the attribute fork
of an inode will be splitted to the next log record, so
we need to check the count of available operations
in the log record and calculate the count of skipped
operations properly.
Signed-off-by: Hou Tao <houtao1@huawei.com>
---
logprint/log_misc.c | 21 ++++++++++++---------
1 file changed, 12 insertions(+), 9 deletions(-)
diff --git a/logprint/log_misc.c b/logprint/log_misc.c
index a0f1766..20f0f89 100644
--- a/logprint/log_misc.c
+++ b/logprint/log_misc.c
@@ -524,6 +524,7 @@ xlog_print_trans_inode(
xfs_inode_log_format_t *f;
int mode;
int size;
+ int printed_ops;
/*
* print inode type header region
@@ -572,13 +573,6 @@ xlog_print_trans_inode(
xlog_print_trans_inode_core(&dino);
*ptr += xfs_log_dinode_size(dino.di_version);
- if (*i == num_ops-1 && f->ilf_size == 3) {
- return 1;
- }
-
- /* does anything come next */
- op_head = (xlog_op_header_t *)*ptr;
-
switch (f->ilf_fields & (XFS_ILOG_DEV | XFS_ILOG_UUID)) {
case XFS_ILOG_DEV:
printf(_("DEV inode: no extra region\n"));
@@ -595,7 +589,13 @@ xlog_print_trans_inode(
ASSERT(f->ilf_size <= 4);
ASSERT((f->ilf_size == 3) || (f->ilf_fields & XFS_ILOG_AFORK));
+ /* does anything come next */
+ printed_ops = 2;
+ op_head = (xlog_op_header_t *)*ptr;
+
if (f->ilf_fields & XFS_ILOG_DFORK) {
+ if (*i == num_ops-1)
+ return f->ilf_size-printed_ops;
(*i)++;
xlog_print_op_header(op_head, *i, ptr);
@@ -618,11 +618,14 @@ xlog_print_trans_inode(
*ptr += be32_to_cpu(op_head->oh_len);
if (op_head->oh_flags & XLOG_CONTINUE_TRANS)
- return 1;
+ return f->ilf_size-printed_ops;
op_head = (xlog_op_header_t *)*ptr;
+ printed_ops++;
}
if (f->ilf_fields & XFS_ILOG_AFORK) {
+ if (*i == num_ops-1)
+ return f->ilf_size-printed_ops;
(*i)++;
xlog_print_op_header(op_head, *i, ptr);
@@ -644,7 +647,7 @@ xlog_print_trans_inode(
}
*ptr += be32_to_cpu(op_head->oh_len);
if (op_head->oh_flags & XLOG_CONTINUE_TRANS)
- return 1;
+ return f->ilf_size-printed_ops;
}
return 0;
--
2.5.0
next reply other threads:[~2017-01-11 13:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 13:38 Hou Tao [this message]
2017-01-12 13:34 ` [PATCH] xfs_logprint: handle the log split of inode item correctly Brian Foster
2017-01-12 14:38 ` Eric Sandeen
2017-01-13 3:28 ` Hou Tao
2017-01-13 3:32 ` Eric Sandeen
2017-01-13 4:23 ` Hou Tao
2017-01-13 15:49 ` Brian Foster
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=1484141938-4195-1-git-send-email-houtao1@huawei.com \
--to=houtao1@huawei.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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).