From: Andreas Dilger <adilger@sun.com>
To: Josef Bacik <jbacik@redhat.com>
Cc: Vegard Nossum <vegard.nossum@gmail.com>,
Josef Bacik <josef@toxicpanda.com>,
linux-ext4@vger.kernel.org, sct@redhat.com,
akpm@linux-foundation.org, 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 17:09:05 -0600 [thread overview]
Message-ID: <20080717230905.GI6239@webber.adilger.int> (raw)
In-Reply-To: <20080717144342.GA15844@unused.rdu.redhat.com>
On Jul 17, 2008 10:43 -0400, Josef Bacik wrote:
> Yeah thats a hard to answer question, one that I will leave up to others
> who have been doing this much longer than I. My thought is remount-ro
> is there to keep you from crashing, so if you have errors=continue then
> you expect to live with the consequences. Course if that bit gets flipped
> via corruption thats not good either.
It shouldn't cause the kernel to crash, but it should definitely return
an error to the application. This is probably one of the code paths
that the Coverity folks were reporting on in FAST this year where on-disk
errors are not propagated to the application.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
next prev parent reply other threads:[~2008-07-17 23:09 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 12:51 ext3 on latest -git: BUG: unable to handle kernel NULL pointer dereference at 0000000c 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
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 [this message]
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=20080717230905.GI6239@webber.adilger.int \
--to=adilger@sun.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@saeurebad.de \
--cc=jbacik@redhat.com \
--cc=josef@toxicpanda.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.com \
--cc=vegard.nossum@gmail.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