From: Willy Tarreau <w@1wt.eu>
To: marcelo@kvack.org
Cc: linux-kernel@vger.kernel.org, Kirill Korotaev <dev@openvz.org>,
Vasily Averin <vvs@sw.ru>, Andrey Savochkin <saw@sawoct.com>,
Dmitry Monakhov <dmonakhov@sw.ru>,
Roberto Nibali <ratz@drugphish.ch>
Subject: [PATCH-2.4] EXT3: ext3 block bitmap leakage
Date: Sat, 1 Jul 2006 07:45:35 +0200 [thread overview]
Message-ID: <20060701054535.GA1459@1wt.eu> (raw)
Hi Marcelo,
we missed this patch sent by Kirill Korotaev on LKML. Fortunately, Roberto
noticed it and forwarded it to me.
Since it's been there for a very long time, there's no emergency, but the
problem looks real and the fix seems to be confirmed, so if you have not
closed 2.4.33 yet, it might be worth merging it too.
Here it is as a git patch, but I've queued it in -upstream if you prefer.
Cheers,
Willy
>From nobody Mon Sep 17 00:00:00 2001
From: Kirill Korotaev <dev@openvz.org>
Date: Fri, 30 Jun 2006 13:41:05 +0400
Subject: [PATCH] EXT3: ext3 block bitmap leakage
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 | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
8c6f6cf38bc9b04edc69c2869ae1e6c584584b4f
diff --git a/fs/ext3/inode.c b/fs/ext3/inode.c
index bcd86f6..d8f5a9b 100644
--- a/fs/ext3/inode.c
+++ b/fs/ext3/inode.c
@@ -570,6 +570,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 */
--
1.3.3
reply other threads:[~2006-07-01 23:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060701054535.GA1459@1wt.eu \
--to=w@1wt.eu \
--cc=dev@openvz.org \
--cc=dmonakhov@sw.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@kvack.org \
--cc=ratz@drugphish.ch \
--cc=saw@sawoct.com \
--cc=vvs@sw.ru \
/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