linux-ext4 - Re: [E2FSPROGS PATCH 1/4] e2fsck: Handle a pass 2 "should never happen" error gracefully

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-id: <20080313054249.GF5851@webber.adilger.int>
Date:	Wed, 12 Mar 2008 23:42:49 -0600
From:	Andreas Dilger <adilger@....com>
To:	"Theodore Ts'o" <tytso@....edu>
Cc:	bas@....tetra.nl, linux-ext4@...r.kernel.org
Subject: Re: [E2FSPROGS PATCH 1/4] e2fsck: Handle a pass 2
 "should never	happen" error gracefully

On Mar 13, 2008  01:12 -0400, Theodore Ts'o wrote:
> --- a/e2fsck/problem.h
> +++ b/e2fsck/problem.h
> @@ -708,6 +708,9 @@ struct problem_context {
>  /* i_blocks_hi should be zero */
>  #define PR_2_BLOCKS_HI_ZERO	0x020044
>  
> +/* Unexpected HTREE block */
> +#define PR_2_UNEXPECTED_HTREE_BLOCK	0x020045

Just an FYI - this problem number conflicts with the "uninit groups"
patch.  Not a fatal problem, but I suspect that with patch-fuzz this
might apply without being noticed.  There is also a problem number
added here in the ibadness-counter patch that should be incremented.

Alternately, if you make this one 0x020048 it won't conflict with either.

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html