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  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]
Date:	Thu, 6 Nov 2008 15:45:21 +0530
From:	"Aneesh Kumar K.V" <>
To:	Theodore Tso <>
	Jindrich Makovicka <>,
Subject: Re: data corruption with ext4 (from exposed by rtorrent

On Wed, Nov 05, 2008 at 03:42:23PM -0500, Theodore Tso wrote:
> On Wed, Nov 05, 2008 at 09:21:00PM +0100, wrote:
> > writes:
> >  >  > The next question is whether the problem is more easily triggerred
> >  >  > when under memory pressure.
> >  > 
> >  > I was currently testing other kernels, but, right, I will retest with more memory.
> > 
> > with -m 2048 I do not observe the problem.
> > 
> > I should add that with 2.6.28-rc3 + ext4 patch queue, I am observing
> > what seems to be lockdep bug:
> > [   31.603020] BUG: key c9f315a8 not in .data!
> Aneesh has some new patches in the ext4 patch queue that add new
> lockdep annotations.  I'm guessing there's a problem there.  Aneesh,
> can you look into this?  Solofo, can you send the .config you used
> in case it was unique to replicating the problem?

The patch aneesh-9-fix-lockdeep-recursive-locking-warning
should add the key in .data.  Do you have a stack trace ?
Can you find out which lock the lockdep is warning about

To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists