From: Adrian Bunk <bunk@stusta.de>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: Kirill Korotaev <dev@openvz.org>,
sct@redhat.com, akpm@linux-foundation.org, adilger@clusterfs.com,
linux-ext4@vger.kernel.org
Subject: [RFC: 2.6.16 patch] ext3: fix ext3 block bitmap leakage
Date: Tue, 20 Feb 2007 16:19:50 +0100 [thread overview]
Message-ID: <20070220151950.GV13958@stusta.de> (raw)
In-Reply-To: <45DA2CB2.4080507@redhat.com>
On Mon, Feb 19, 2007 at 06:03:14PM -0500, Chuck Ebbert wrote:
> This was dropped from 2.6.16-stable somehow:
>
> http://lkml.org/lkml/2006/6/30/54
Thanks for forwarding it.
This patch didn't went in this form into Linus' tree, I'd therefore like
to get an ACK from the ext3 maintainers (Cc'ed) before applying it.
> Below is probably mangled by Thunderbird, you'll have
> to fetch it yourself if you want to merge it:
patch(1) has a nice -l option for applying such patches. :-)
> From: Kirill Korotaev <>
>
> This patch fixes ext3 block bitmap leakage,
> which leads to the following fsck messages on
> _healthy_ filesystem:
> Block bitmap differences: -64159 -73707
>
> All kernels up to 2.6.17 have this bug.
>
> Found by
> Vasily Averin <vvs@sw.ru> and Andrey Savochkin <saw@sawoct.com>
> Test case triggered the issue was created by
> Dmitry Monakhov <dmonakhov@sw.ru>
>
> Signed-Off-By: Vasiliy Averin <vvs@sw.ru>
> Signed-Off-By: Andrey Savochkin <saw@sawoct.com>
> Signed-Off-By: Kirill Korotaev <dev@openvz.org>
> CC: Dmitry Monakhov <dmonakhov@sw.ru>
>
> --- ./fs/ext3/inode.c.e3crp 2006-06-28 05:22:40.000000000 +0400
> +++ ./fs/ext3/inode.c 2006-06-27 13:31:20.000000000 +0400
> @@ -585,6 +585,7 @@ static int ext3_alloc_branch(handle_t *h
>
> branch[0].key = cpu_to_le32(parent);
> if (parent) {
> + keys = 1;
> for (n = 1; n < num; n++) {
> struct buffer_head *bh;
> /* Allocate the next block */
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next parent reply other threads:[~2007-02-20 15:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <45DA2CB2.4080507@redhat.com>
2007-02-20 15:19 ` Adrian Bunk [this message]
2007-02-20 17:08 ` [RFC: 2.6.16 patch] ext3: fix ext3 block bitmap leakage Eric Sandeen
2007-02-26 14:35 ` Adrian Bunk
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=20070220151950.GV13958@stusta.de \
--to=bunk@stusta.de \
--cc=adilger@clusterfs.com \
--cc=akpm@linux-foundation.org \
--cc=cebbert@redhat.com \
--cc=dev@openvz.org \
--cc=linux-ext4@vger.kernel.org \
--cc=sct@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.