From: Theodore Tso <tytso@mit.edu>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: BUG: unable to handle kernel NULL pointer dereference at 00000000 [ext4_new_meta_blocks+0x7c/0xb7]
Date: Fri, 12 Dec 2008 09:56:09 -0500 [thread overview]
Message-ID: <20081212145609.GA26085@mit.edu> (raw)
In-Reply-To: <20081209104121.GA7572@skywalker>
On Tue, Dec 09, 2008 at 04:11:22PM +0530, Aneesh Kumar K.V wrote:
> The problem is due to remove-do_blk_alloc patch.
>
> The patch below should fix the crash.
>
> - EXT4_I(inode)->i_allocated_meta_blocks += *count;
> + EXT4_I(inode)->i_allocated_meta_blocks += ar.len;
Good catch, thanks. I'll add it to the patch queue.
> I have one question regarding the patch. What about blocks allocated for
> directories for the ext3 format. With extent format we are not
> setting EXT4_MB_HINT_DATA for non regular files. So i guess we also
> need the below patch .
One of the good things about getting rid of too many layers of
abstractions is that it makes bugs like this easier to spot. We've
been sending allocating directory and symlinks using EXT4_MB_HINT_DATA
if extents haven't been enabled, and no one noticed before we
simplified out things....
Actually, I wonder if maybe we should set EXT4_MB_HINT_DATA for
directories as well. Making directories contiguous does speed up
certain workloads, and it does speed up fsck. It may be though that
the mballoc algorithms should be tuned specifically for directories,
and what we should do is to define a new flag, EXT4_MB_HINT_DIRECTORY,
and pass it in for that case.
Some experimentation is clearly called for, here....
- Ted
next prev parent reply other threads:[~2008-12-12 14:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-09 10:41 BUG: unable to handle kernel NULL pointer dereference at 00000000 [ext4_new_meta_blocks+0x7c/0xb7] Aneesh Kumar K.V
2008-12-12 14:56 ` Theodore Tso [this message]
2008-12-17 7:56 ` Aneesh Kumar K.V
2008-12-17 11:47 ` Theodore Tso
2008-12-17 16:25 ` Aneesh Kumar K.V
2008-12-18 8:55 ` Andreas Dilger
2009-01-02 5:08 ` 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=20081212145609.GA26085@mit.edu \
--to=tytso@mit.edu \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-ext4@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).