DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=fdcx7IfLtvyj4hpXZiLTUG4l1Q38nc5nXwu8agBAcdU0LtU0hWMfhij/5S9ahjbZP4
         1ma0VgGsCgAnSV8o5NuK67anV5+5rWA8ZpnQIofWodwOQtCcK9dTFTFLdG08vw58HNz1
         mXTwAFTHa9MrJUByF9U//MJmRwrj4tRiqGJRg=
Message-ID: <19f34abd0807170639p838d14blc9a13d2104313f38@mail.gmail.com>
Date: Thu, 17 Jul 2008 15:39:24 +0200
From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Josef Bacik" <josef@toxicpanda.com>
Subject: Re: ext3 on latest -git: BUG: unable to handle kernel NULL pointer dereference at 0000000c
Cc: linux-ext4@vger.kernel.org, sct@redhat.com, akpm@linux-foundation.org,
       adilger@sun.com, "Johannes Weiner" <hannes@saeurebad.de>,
       linux-kernel@vger.kernel.org
In-Reply-To: <1b7401870807170634u14492a53k3931ddcddbd1e098@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <19f34abd0807170551q4fbb862bu270297cfd76a69be@mail.gmail.com>
	 <1b7401870807170613y747baa7by158177047cc7e28@mail.gmail.com>
	 <19f34abd0807170620g39ab942bl592ea3fa3fa0dab@mail.gmail.com>
	 <1b7401870807170634u14492a53k3931ddcddbd1e098@mail.gmail.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1308
Lines: 45

On Thu, Jul 17, 2008 at 3:34 PM, Josef Bacik <josef@toxicpanda.com> wrote:
>> Yeah, the full log exists at
>>
>>    http://folk.uio.no/vegardno/linux/log-1216293934.txt
>>
>> I think this is the interesting part:
>
> Hmm well the journal should have aborted, but it looks like it didn't,
> are you mounting with errors=continue by any chance?  Thanks much,

No, this is the command I used:

        mount -o loop disk mnt

I think this looks interesting:

EXT3-fs error (device loop0) in ext3_reserve_inode_write: IO failure

The code in ext3_reserve_inode_write() is here:

        err = ext3_journal_get_write_access(handle, iloc->bh);
        if (err) {
                brelse(iloc->bh);
                iloc->bh = NULL;
        }

Maybe it should do something different here?

But I don't know :-)

Thanks for helping out!


Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/