mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Josef Bacik" <josef@toxicpanda.com>
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
Subject: Re: ext3 on latest -git: BUG: unable to handle kernel NULL pointer dereference at 0000000c
Date: Thu, 17 Jul 2008 15:39:24 +0200	[thread overview]
Message-ID: <19f34abd0807170639p838d14blc9a13d2104313f38@mail.gmail.com> (raw)
In-Reply-To: <1b7401870807170634u14492a53k3931ddcddbd1e098@mail.gmail.com>

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

  reply	other threads:[~2008-07-17 13:39 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-17 12:51 Vegard Nossum
2008-07-17 13:13 ` Josef Bacik
2008-07-17 13:20   ` Vegard Nossum
2008-07-17 13:34     ` Josef Bacik
2008-07-17 13:39       ` Vegard Nossum [this message]
2008-07-17 13:40         ` Josef Bacik
2008-07-17 13:57         ` Josef Bacik
2008-07-17 14:25           ` Vegard Nossum
2008-07-17 14:13             ` Josef Bacik
2008-07-17 14:35               ` Vegard Nossum
2008-07-17 14:16                 ` Josef Bacik
2008-07-17 14:44                   ` Vegard Nossum
2008-07-17 14:33                     ` Josef Bacik
2008-07-17 15:00                       ` Vegard Nossum
2008-07-17 14:43                         ` Josef Bacik
2008-07-17 23:09                           ` Andreas Dilger
2008-07-18 10:51                             ` Josef Bacik
2008-07-18 11:32                               ` Vegard Nossum
2008-07-18 11:20                                 ` Josef Bacik
2008-07-18 11:58                                   ` Vegard Nossum
2008-07-18 20:28                                     ` Vegard Nossum
2008-07-17 15:08                     ` Theodore Tso
2008-07-17 15:16                       ` Vegard Nossum
2008-07-17 15:40                         ` Theodore Tso
2008-07-17 23:06                           ` Andreas Dilger

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=19f34abd0807170639p838d14blc9a13d2104313f38@mail.gmail.com \
    --to=vegard.nossum@gmail.com \
    --cc=adilger@sun.com \
    --cc=akpm@linux-foundation.org \
    --cc=hannes@saeurebad.de \
    --cc=josef@toxicpanda.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sct@redhat.com \
    /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®