linux-ext4 - Re: ext3: kernel BUG at fs/jbd/journal.c:412!

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20081106164326.GG25194@skywalker>
Date:	Thu, 6 Nov 2008 22:13:26 +0530
From:	"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>
To:	Arthur Jones <ajones@...erbed.com>
Cc:	Ext4 Developers List <linux-ext4@...r.kernel.org>
Subject: Re: ext3: kernel BUG at fs/jbd/journal.c:412!

On Thu, Nov 06, 2008 at 08:12:27AM -0800, Arthur Jones wrote:
> Hi Aneesh, ...
> 
> On Thu, Nov 06, 2008 at 07:50:25AM -0800, Aneesh Kumar K.V wrote:
> > I get this with ext4-patchqueue. I guess we have some ext3 patches queued there.
> 
> This could be related to a patch I just posted.
> 
> I'd like to try to reproduce this.  What is the
> ext4-patchqueue?  What were you running that caused
> this to pop up?

I got it while running fsstress with mem=128MB kernel option.
I can also reproduce it while running http://lkml.org/lkml/2006/12/27/180

> 
> See the thread on linux-ext4 called "ext3: slow symlink corruption
> on umount" for details on how this patch came about...
> 
> Thanks...
> 

-aneesh
--
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