From: Miao Xie <miaox@cn.fujitsu.com>
To: tytso@mit.edu
Cc: linux-ext4@vger.kernel.org
Subject: [PATCH] [e2fsprogs] e2fsck: fix segmentation fault when block size is greater than 8192
Date: Wed, 17 Dec 2008 16:58:12 +0800 [thread overview]
Message-ID: <4948BF24.3040601@cn.fujitsu.com> (raw)
When I did fsck a filesystem with large blocksize(greater than 8192),
segmentation fault occured. The cause is the size of b_data array that is
defined as a fixed size in buffer_head structure.
(File: e2fsck/jfs_user.h)
struct buffer_head {
char b_data[8192];
e2fsck_t b_ctx;
io_channel b_io;
int b_size;
blk_t b_blocknr;
int b_dirty;
int b_uptodate;
int b_err;
};
It is unreasonable, because if the blocksize is greater than 8192, b_data will
overflow and the other variable would be changed, then if we touch those
variable, segmentation fault occurs.
This patch fixes this bug.
Signed-off-by: Miao Xie <miaox@cn.fujitsu.com>
---
e2fsck/jfs_user.h | 2 +-
e2fsck/journal.c | 8 ++++++++
2 files changed, 9 insertions(+), 1 deletions(-)
diff --git a/e2fsck/jfs_user.h b/e2fsck/jfs_user.h
index 0e4f951..f042218 100644
--- a/e2fsck/jfs_user.h
+++ b/e2fsck/jfs_user.h
@@ -15,7 +15,7 @@
#include "e2fsck.h"
struct buffer_head {
- char b_data[8192];
+ char * b_data;
e2fsck_t b_ctx;
io_channel b_io;
int b_size;
diff --git a/e2fsck/journal.c b/e2fsck/journal.c
index 10f5095..ca7a4c3 100644
--- a/e2fsck/journal.c
+++ b/e2fsck/journal.c
@@ -73,6 +73,12 @@ struct buffer_head *getblk(kdev_t kdev, blk_t blocknr, int blocksize)
if (!bh)
return NULL;
+ bh->b_data = e2fsck_allocate_memory(kdev->k_ctx, blocksize,
+ "block buffer b_data");
+ if (!bh->b_data) {
+ ext2fs_free_mem(&bh);
+ return NULL;
+ }
#ifdef CONFIG_JBD_DEBUG
if (journal_enable_debug >= 3)
bh_count++;
@@ -163,6 +169,8 @@ void brelse(struct buffer_head *bh)
ll_rw_block(WRITE, 1, &bh);
jfs_debug(3, "freeing block %lu/%p (total %d)\n",
(unsigned long) bh->b_blocknr, (void *) bh, --bh_count);
+ if (bh->b_data)
+ ext2fs_free_mem(&bh->b_data);
ext2fs_free_mem(&bh);
}
--
1.5.4.rc3
next reply other threads:[~2008-12-17 8:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-17 8:58 Miao Xie [this message]
2009-01-02 23:30 ` [PATCH] [e2fsprogs] e2fsck: fix segmentation fault when block size is greater than 8192 Theodore Tso
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=4948BF24.3040601@cn.fujitsu.com \
--to=miaox@cn.fujitsu.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).