linux-kernel - Re: ext3 on latest -git: BUG: unable to handle kernel NULL pointer dereference at 0000000c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080717144342.GA15844@unused.rdu.redhat.com>
Date:	Thu, 17 Jul 2008 10:43:42 -0400
From:	Josef Bacik <jbacik@...hat.com>
To:	Vegard Nossum <vegard.nossum@...il.com>
Cc:	Josef Bacik <jbacik@...hat.com>,
	Josef Bacik <josef@...icpanda.com>, 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 05:00:07PM +0200, Vegard Nossum wrote:
> On Thu, Jul 17, 2008 at 4:33 PM, Josef Bacik <jbacik@...hat.com> wrote:
> > Ok run dumpe2fs -h on your image and see if you have a line that says
> >
> > Errors behavior:          Continue
> >
> > if you do run tune2fs -e remount-ro and then do the mount.  That would explain
> > why you are still having panics even though we should be aborting the journal.
> > Thanks,
> 
> Ahh, that probably explains it. I didn't realize there was such a thing.
> 
> I am doing random-corruption tests, so it is quite possible that this
> bit gets set anywhere along the road...
> 
> But even so, is it correct that the kernel should crash? It seems
> quite possible that error behaviour can change (like this) even with
> "normal" corruption, e.g. outside my test scripts.
>

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.  Thanks,

Josef
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/