[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <19f34abd0807170639p838d14blc9a13d2104313f38@mail.gmail.com>
Date: Thu, 17 Jul 2008 15:39:24 +0200
From: "Vegard Nossum" <vegard.nossum@...il.com>
To: "Josef Bacik" <josef@...icpanda.com>
Cc: linux-ext4@...r.kernel.org, sct@...hat.com,
akpm@...ux-foundation.org, adilger@....com,
"Johannes Weiner" <hannes@...urebad.de>,
linux-kernel@...r.kernel.org
Subject: Re: ext3 on latest -git: BUG: unable to handle kernel NULL pointer dereference at 0000000c
On Thu, Jul 17, 2008 at 3:34 PM, Josef Bacik <josef@...icpanda.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-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists