linux-ext4 - Re: [PATCH] ext4: critical info format fix in __ext4_grp_locked

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110322004739.GJ4135@thunk.org>
Date:	Mon, 21 Mar 2011 20:47:39 -0400
From:	Ted Ts'o <tytso@....edu>
To:	Robin Dong <hao.bigrat@...il.com>
Cc:	linux-ext4@...r.kernel.org, Robin Dong <sanbai@...bao.com>,
	Tao Ma <boyu.mt@...bao.com>
Subject: Re: [PATCH] ext4: critical info format fix in
 __ext4_grp_locked_error

Applied to the ext4 patch queue.

On Fri, Mar 18, 2011 at 05:58:03PM +0800, Robin Dong wrote:
> From: Robin Dong <sanbai@...bao.com>
> 
> When we do performence-testing on ext4 filesystem, we observe a warning like this:
> 
> "[ 1684.113205] EXT4-fs error (device sda7): ext4_mb_generate_buddy:718: group 259825901 blocks in bitmap, 26057 in gd"
> 
> indeed, it should be
> 
> "group 2598, 25901 blocks in bitmap, 26057 in gd"

Note that the next two paragraphs don't really belong in a commit
description.  It's best if you put this kind of stuff after the
signed-off-by lines, with a "---" separating the commit description, like this:

Signed off by: Ty Coon <tycoon@...il.com>
---
Stuff that explains the context of the patch

diff --git ....

> This bug is found on upstream 2.6.36 kernel. We ran a 2.6.36 kernel
> on the online system with 8 Ext4 file systems. 2 of them are mounted
> with delayed allocation feature. This warning is only observed on
> delayed allocation enabled Ext4 file systems.
> 
> This issue is not easy to reproduce, on two servers with 2.6.36
> kenrel + ext4, after running 110+ days, the error starts to appear
> on kernel log. When check the error log, we found the info format
> should be fixed, that's how this patch comes.

Can you send more information about what sort of workloads your
servers are under, and any other information about how to reproduce
it?

						- Ted
--
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