From: "Hans-Peter Jansen" <hpj@urpla.net>
To: xfs@oss.sgi.com
Subject: Re: 2.6.34-rc3: simple du (on a big xfs tree) triggers oom killer [bisected: 57817c68229984818fea9e614d6f95249c3fb098]
Date: Sat, 24 Apr 2010 18:44:22 +0200
User-Agent: KMail/1.9.10
Cc: Dave Chinner <david@fromorbit.com>, opensuse-kernel@opensuse.org,
       linux-kernel@vger.kernel.org, Greg KH <gregkh@suse.de>,
       Nick Piggin <npiggin@suse.de>
References: <201004050049.17952.hpj@urpla.net> <20100413091823.GD7544@dastard> <201004131142.33518.hpj@urpla.net>
In-Reply-To: <201004131142.33518.hpj@urpla.net>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <201004241844.23482.hpj@urpla.net>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1868
Lines: 48

On Tuesday 13 April 2010, 11:42:33 Hans-Peter Jansen wrote:
> On Tuesday 13 April 2010, 11:18:23 Dave Chinner wrote:
> > On Tue, Apr 13, 2010 at 10:50:35AM +0200, Hans-Peter Jansen wrote:
> > > Dave, may I ask you kindly for briefly elaborating on the worst
> > > consequences of just reverting this hunk, as I've done before?
> >
> > Well, given that is the new shrinker code generating the warnings,
> > reverting/removing that hunk will render the patch useless :0
>
> Excuse me, I didn't express myself well. I'm after the consequences of
> applying the revert, that I posted a few messages above.
>
> > I'll get you a working 2.6.33 patch tomorrow - it's dinner time
> > now....
>
> Cool, thanks.

Obviously and not totally unexpected, really fixing this is going to take 
more time.

FYI, 2.6.33.2 is still affected from this issue. 

Greg, you might search for a server using xfs filesystems and and a i586 
kernel >= 2.6.33, (2.6.32.11 of SLE11-SP1 will serve as well), log in as an 
ordinary user, do a "du" on /usr, and wait for the other users screaming...

BTW, all affected kernels, available from 
http://download.opensuse.org/repositories/home:/frispete: have the 
offending patch reverted (see subject), do run fine for me (on this 
aspect).

Will you guys pass by another round of stable fixes without doing anything 
on this issue?

Dave, this is why I'm kindly asking you: what might be the worst 
consequences, if we just do the revert for now (at least for 2.6.33), until 
you and Nick came to a final decision on how to solve this issue in the 
future.

Just a brief note would be fine.

Cheers,
Pete
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/