From: rpeterso@sourceware.org <rpeterso@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/gfs2/fsck metawalk.c
Date: 26 Feb 2007 19:19:07 -0000 [thread overview]
Message-ID: <20070226191907.7804.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Changes by: rpeterso at sourceware.org 2007-02-26 19:19:06
Modified files:
gfs2/fsck : metawalk.c
Log message:
Resolves bz: 229222: gfs2_fsck stuck in infinite loop
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs2/fsck/metawalk.c.diff?cvsroot=cluster&r1=1.7&r2=1.8
--- cluster/gfs2/fsck/metawalk.c 2007/01/23 19:44:12 1.7
+++ cluster/gfs2/fsck/metawalk.c 2007/02/26 19:19:06 1.8
@@ -96,6 +96,15 @@
}
}
+ if (de.de_rec_len < sizeof(struct gfs2_dirent)) {
+ log_err("Entry %" PRIu64 "(0x%"
+ PRIx64 ") of directory %" PRIu64 "(0x%"
+ PRIx64 ") is corrupt, skipping.\n",
+ bh->b_blocknr, bh->b_blocknr,
+ ip->i_di.di_num.no_addr,
+ ip->i_di.di_num.no_addr);
+ break;
+ }
if ((char *)dent + de.de_rec_len >= bh_end){
log_debug("Last entry processed.\n");
break;
@@ -180,6 +189,15 @@
*update = updated;
}
+ /* Make sure it's really a leaf. */
+ if (leaf.lf_header.mh_type != GFS2_METATYPE_LF) {
+ log_err("Inode %" PRIu64 " (0x%"
+ PRIx64 ") points to bad leaf "
+ PRIu64 " (0x%" PRIx64 ").\n",
+ ip->i_di.di_num.no_addr, leaf_no);
+ brelse(lbh, *update);
+ break;
+ }
exp_count = (1 << (ip->i_di.di_depth - leaf.lf_depth));
log_debug("expected count %u - di_depth %u, leaf depth %u\n",
exp_count, ip->i_di.di_depth, leaf.lf_depth);
next reply other threads:[~2007-02-26 19:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-26 19:19 rpeterso [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-26 19:20 [Cluster-devel] cluster/gfs2/fsck metawalk.c rpeterso
2007-01-23 19:54 rpeterso
2007-01-23 19:44 rpeterso
2006-11-20 21:46 rpeterso
2006-11-20 21:30 rpeterso
2006-11-20 15:44 rohara
2006-11-20 15:35 rpeterso
2006-11-16 20:12 rohara
2006-11-16 19:56 rohara
2006-11-14 22:55 rpeterso
2006-11-14 22:51 rpeterso
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=20070226191907.7804.qmail@sourceware.org \
--to=rpeterso@sourceware.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).