xfs
[Top] [All Lists]

Re: inode_permission NULL pointer dereference in 3.13-rc1

To: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Subject: Re: inode_permission NULL pointer dereference in 3.13-rc1
From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
Date: Wed, 27 Nov 2013 06:43:51 +0000
Cc: linux-fsdevel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <20131126141253.GA28062@xxxxxxxxxxxxx>
References: <20131124140413.GA19271@xxxxxxxxxxxxx> <20131124152758.GL10323@xxxxxxxxxxxxxxxxxx> <20131125160648.GA4933@xxxxxxxxxxxxx> <20131126131134.GM10323@xxxxxxxxxxxxxxxxxx> <20131126141253.GA28062@xxxxxxxxxxxxx>
Sender: Al Viro <viro@xxxxxxxxxxxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
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.

Setup is kvm on 3.3GHz amd64 6-core, with 4Gb given to guest (after having
one too many OOMs on leaks).  virtio disk, with raw image sitting in a file
on host, xfstests from current git, squeeze/amd64 userland on guest.
Reasonably fast host disks (not that the sucker had been IO-bound, anyway).
Tried both with UP and 4-way SMP guest, same picture on both...

<Prev in Thread] Current Thread [Next in Thread>