From: Yasunori Goto <y-goto@jp.fujitsu.com>
To: tytso@mit.edu, adilger@sun.com
Cc: Li Zefan <lizf@cn.fujitsu.com>,
linux-ext4@vger.kernel.org, Miao Xie <miaox@cn.fujitsu.com>,
Linux Kernel ML <linux-kernel@vger.kernel.org>
Subject: [Patch/BUG] (ext4) s_mb_maxs[] of ext4_sb_info is too small size
Date: Tue, 16 Dec 2008 17:25:44 +0900 [thread overview]
Message-ID: <20081216170409.34EA.E1E9C6FF@jp.fujitsu.com> (raw)
Hello.
I chased the cause of following ext4 oops report which is tested on
ia64 box.
http://bugzilla.kernel.org/show_bug.cgi?id=12018
The cause is the size of s_mb_maxs array that is
defined as "unsigned short" in ext4_sb_info structure.
Unsigned short is too small.
In this bug report, Li-san formatted with 64Kbyte block size like
the following. Ia64 has 64Kbyte page size, then this
block size is acceptable.
# mkfs.ext4 -b 65536 /dev/md0
In this case, the maximum value of s_mb_maxs[] becomes
(blocksize << 2) = 256K by the following code.
2482 int ext4_mb_init(struct super_block *sb, int needs_recovery)
:
:
2508 max = sb->s_blocksize << 2; <---- max becomes 0x40000.
2509 do {
2510 sbi->s_mb_offsets[i] = offset;
2511 sbi->s_mb_maxs[i] = max; <--- over flow!!!
2512 offset += 1 << (sb->s_blocksize_bits - i);
2513 max = max >> 1;
2514 i++;
2515 } while (i <= sb->s_blocksize_bits + 1);
Then, some s_mb_maxs[] becomes 0 due to overflow.
It is cause of this oops. The following patch is to fix it.
Thanks.
----
The size of s_mb_maxs that is defined in ext4_sb_info is too small.
When block size is 64K, which is possible on ia64,
the maximum value of s_mb_maxs becomes 256K(0x40000).
However, s_mb_maxs is defined as unsigned short. This is cause of panic.
Signed-off-by: Yasunori Goto <y-goto@jp.fujitsu.com>
Cc: Li Zefan <lizf@cn.fujitsu.com>
Cc: Miao Xie <miaox@cn.fujitsu.com>
---
fs/ext4/ext4_sb.h | 3 ++-
fs/ext4/mballoc.c | 2 ++
2 files changed, 4 insertions(+), 1 deletion(-)
Index: test2/fs/ext4/ext4_sb.h
===================================================================
--- test2.orig/fs/ext4/ext4_sb.h 2008-12-16 11:20:18.000000000 +0900
+++ test2/fs/ext4/ext4_sb.h 2008-12-16 14:17:32.000000000 +0900
@@ -101,7 +101,8 @@ struct ext4_sb_info {
spinlock_t s_reserve_lock;
spinlock_t s_md_lock;
tid_t s_last_transaction;
- unsigned short *s_mb_offsets, *s_mb_maxs;
+ unsigned short *s_mb_offsets;
+ unsigned int *s_mb_maxs;
/* tunables */
unsigned long s_stripe;
Index: test2/fs/ext4/mballoc.c
===================================================================
--- test2.orig/fs/ext4/mballoc.c 2008-12-16 11:20:18.000000000 +0900
+++ test2/fs/ext4/mballoc.c 2008-12-16 14:23:21.000000000 +0900
@@ -2493,6 +2493,8 @@ int ext4_mb_init(struct super_block *sb,
if (sbi->s_mb_offsets == NULL) {
return -ENOMEM;
}
+
+ i = (sb->s_blocksize_bits + 2) * sizeof(unsigned int);
sbi->s_mb_maxs = kmalloc(i, GFP_KERNEL);
if (sbi->s_mb_maxs == NULL) {
kfree(sbi->s_mb_maxs);
--
Yasunori Goto
next reply other threads:[~2008-12-16 8:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 8:25 Yasunori Goto [this message]
2008-12-16 16:58 ` Eric Sandeen
2008-12-17 2:45 ` Yasunori Goto
2008-12-17 5:59 ` 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=20081216170409.34EA.E1E9C6FF@jp.fujitsu.com \
--to=y-goto@jp.fujitsu.com \
--cc=adilger@sun.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=miaox@cn.fujitsu.com \
--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
all inboxes | Powered by JetHome®