linux-kernel - Re: Kernel 2.6.30.4 XFS(..?) regression (happened again)

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: <alpine.DEB.2.00.0908171024380.12533@p34.internal.lan>
Date:	Mon, 17 Aug 2009 10:25:22 -0400 (EDT)
From:	Justin Piszcz <jpiszcz@...idpixels.com>
To:	Christoph Hellwig <hch@...radead.org>
cc:	Felix Blyakher <felixb@....com>, linux-kernel@...r.kernel.org,
	xfs@....sgi.com
Subject: Re: Kernel 2.6.30.4 XFS(..?) regression (happened again)



On Sat, 15 Aug 2009, Christoph Hellwig wrote:

> All your traces seem to have in common that you're block on locks hold
> by processed doing I/O.  Especially a lot of page locks which are
> controlled by the VM and not the filesystem.  Can you try with commit
> 8aa7e847d834ed937a9ad37a0f2ad5b8584c1ab0 from 2.6.31-rc applied, or
> better directly 2.6.3-rc6?
>
> I would be surprised if this is something inside XFS, but running with
> CONFIG_XFS_DEBUG never hurts.
>

Christoph,

Thanks, running with DEBUG and 2.6.31-rc6.

CONFIG_XFS_DEBUG=y

So far the problem has not surfaced, but it normally takes 24-48 hours.

Justin.
--
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/