From: Tao Ma <tm@tao.ma>
To: Robin Dong <hao.bigrat@gmail.com>
Cc: linux-ext4@vger.kernel.org, Robin Dong <sanbai@taobao.com>,
stable-commits@vger.kernel.org
Subject: Re: [PATCH] ext4: critical info format fix in __acquire
Date: Wed, 16 Mar 2011 22:52:06 +0800 [thread overview]
Message-ID: <4D80CE96.1080300@tao.ma> (raw)
In-Reply-To: <1300268245-18752-1-git-send-email-hao.bigrat@gmail.com>
Hi Robin,
The function that has the problem isn't ;__acquire', but
__ext4_grp_locked_error. the description __acquire is used for sparse
check. So I guess it is a little misleading for the subject. Please
change it. Thanks.
btw, You can add Cc: stable@kernel.org in your patch if you want this
patch to be in stable.
Regards,
Tao
On 03/16/2011 05:37 PM, Robin Dong wrote:
> From: Robin Dong <sanbai@taobao.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.
>
> Reviewed-by: Coly Li <bosong.ly@taobao.com>
> Signed-off-by: Robin Dong <sanbai@taobao.com>
> ---
> fs/ext4/super.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/fs/ext4/super.c b/fs/ext4/super.c
> index f6a318f..bb38475 100644
> --- a/fs/ext4/super.c
> +++ b/fs/ext4/super.c
> @@ -594,7 +594,7 @@ __acquires(bitlock)
>
> vaf.fmt = fmt;
> vaf.va = &args;
> - printk(KERN_CRIT "EXT4-fs error (device %s): %s:%d: group %u",
> + printk(KERN_CRIT "EXT4-fs error (device %s): %s:%d: group %u, ",
> sb->s_id, function, line, grp);
> if (ino)
> printk(KERN_CONT "inode %lu: ", ino);
prev parent reply other threads:[~2011-03-16 14:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 9:37 [PATCH] ext4: critical info format fix in __acquire Robin Dong
2011-03-16 10:42 ` Coly Li
2011-03-16 14:52 ` Tao Ma [this message]
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=4D80CE96.1080300@tao.ma \
--to=tm@tao.ma \
--cc=hao.bigrat@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sanbai@taobao.com \
--cc=stable-commits@vger.kernel.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).