On Wed, Nov 27, 2013 at 06:43:51AM +0000, Al Viro wrote: > On Tue, Nov 26, 2013 at 06:12:53AM -0800, Christoph Hellwig wrote: > > On Tue, Nov 26, 2013 at 01:11:34PM +0000, Al Viro wrote: > > > .config, please - all I'm seeing on mine is a bloody awful leak somewhere > > > in VM that I'd been hunting for last week, so the damn thing gets OOMed > > > halfway through xfstests run ;-/ > > > # > > # Automatically generated file; DO NOT EDIT. > > # Linux/x86 3.12.0-hubcap2 Kernel Configuration > [snip] > > Could you post the output of your xfstests run? FWIW, with your .config > I'm seeing the same leak (shut down by turning spinlock debugging off, > it's split page table locks that end up leaking when they are separately > allocated) *and* xfs/253 seems to be sitting there indefinitely once > we get to it - about 100% system time, no blocked processes, xfs_db running > all the time for hours. No oopsen on halt with that sucker skipped *or* > interrupted halfway through. IOWs, you've got a version of xfs_db that has the infinite loop bug that the xfs/253 is trying to tickle: # This test was created to verify fixes for problems where metadump # would never complete due to an inability to find a suitable # obfuscated name to use. Upgrade your xfsprogs package to 3.1.11 and the problem should go away. Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
