[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e9e943910709101835t413753d3j3c4b3cf2fa769d72@mail.gmail.com>
Date: Tue, 11 Sep 2007 02:35:04 +0100
From: "Duane Griffin" <duaneg@...da.com>
To: "Eric Sandeen" <sandeen@...hat.com>
Cc: "linux-kernel Mailing List" <linux-kernel@...r.kernel.org>,
"Andrew Morton" <akpm@...ux-foundation.org>,
"ext4 development" <linux-ext4@...r.kernel.org>
Subject: Re: [PATCH V2] dir_index: error out instead of BUG on corrupt dx dirs
On 10/09/2007, Eric Sandeen <sandeen@...hat.com> wrote:
> I don't know if it's worth differentiating messages for different types
> of corruption (root block vs. others, etc...) - I guess the other error
> cases do.
Might be useful for a developer wanting to know exactly which error
check was triggering. Unlikely to be of much interest or use to the
user, so I wouldn't worry too much about the exact wording.
> Here's a patch rolling up yours with mine + discussed changes, and
> consolidating the fsck suggestion message.
>
> How's it look to you? Suppose I'd better run this a bit to be sure it's
> not hitting any common cases and issuing new warnings...?
The warnings shouldn't include explicit newlines, aside from that it
looks good to me. I've tested it with the corruption utility and all
combinations (count & limit, root & indirect) seem to work correctly.
> Signed-off-by: Eric Sandeen <sandeen@...hat.com>
Acked-by: Duane Griffin <duaneg@...da.com>
Cheers,
Duane.
--
"I never could learn to drink that blood and call it wine" - Bob Dylan
-
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
Powered by blists - more mailing lists