Message ID | 20141027171000.GA10057@birch.djwong.org |
---|---|
State | Superseded, archived |
Headers | show |
On Mon, Oct 27, 2014 at 10:10:00AM -0700, Darrick J. Wong wrote: > On Sun, Oct 26, 2014 at 12:47:09PM +0200, Sami Liedes wrote: > > On Mon, Oct 20, 2014 at 01:57:36PM -0700, Darrick J. Wong wrote: > > > Thanks for catching these! I'll have patches out shortly. > > > > Great! With your patches applied I could no longer get any valgrind > > errors on ext4 during overnight fuzz testing. > > > > Here's one more I found which only shows on ext[23], with or without > > your recent patches. It seems that the error message "Unexpected block > > in HTREE directory inode %d (%q)" is printed with uninitialized values > > for both the %d and the %q conversions. > > I think the following patch fixes this problem; can you give it a spin? Yeah, that seems to fix it. Sami
diff --git a/e2fsck/pass2.c b/e2fsck/pass2.c index fa17f20..f645229 100644 --- a/e2fsck/pass2.c +++ b/e2fsck/pass2.c @@ -1006,6 +1006,7 @@ inline_read_fail: dx_dir = e2fsck_get_dx_dir_info(ctx, ino); if (dx_dir && dx_dir->numblocks) { if (db->blockcnt >= dx_dir->numblocks) { + pctx.dir = ino; if (fix_problem(ctx, PR_2_UNEXPECTED_HTREE_BLOCK, &pctx)) { clear_htree(ctx, ino);