netdev
[Top] [All Lists]

Re: kernel BUG at page_alloc.c:98 -- compiling with distcc

To: Andrew Morton <akpm@xxxxxxxx>
Subject: Re: kernel BUG at page_alloc.c:98 -- compiling with distcc
From: Andrea Arcangeli <andrea@xxxxxxx>
Date: Fri, 30 Apr 2004 02:15:21 +0200
Cc: marcelo.tosatti@xxxxxxxxxxxx, jmoyer@xxxxxxxxxx, carson@xxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx, davem@xxxxxxxxxx
In-reply-to: <20040429162632.689fa7fe.akpm@osdl.org>
References: <382320000.1082759593@taltos.ny.ficc.gs.com> <16527.4259.174536.629347@segfault.boston.redhat.com> <20040429210951.GB20453@logos.cnet> <20040429142807.1fa4c5ea.akpm@osdl.org> <20040429224936.GT29954@dualathlon.random> <20040429162632.689fa7fe.akpm@osdl.org>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mutt/1.4.1i
On Thu, Apr 29, 2004 at 04:26:32PM -0700, Andrew Morton wrote:
> The only application which we know will exercise that code is the distcc
> server.  Making that little change while testing the patch will increase
> the chance of shaking out any problems.

if you're scared it has bugs I think it'd be more useful to change it to
"|| 1" and run it under some stress test, and then remove the "|| 1".
the aio code in unmap_kvec is also a big user of that.  a schedule every
40M of ram freed isn't too nice to my eyes (but I doubt it can be
measured).

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