[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080416125921.GI9191@parisc-linux.org>
Date: Wed, 16 Apr 2008 06:59:21 -0600
From: Matthew Wilcox <matthew@....cx>
To: Andi Kleen <andi@...stfloor.org>
Cc: Ingo Molnar <mingo@...e.hu>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Peter Zijlstra <peterz@...radead.org>,
Bart Van Assche <bart.vanassche@...il.com>,
Roland Dreier <rdreier@...co.com>,
Ingo Oeser <ioe-lkml@...eria.de>,
Daniel Walker <dwalker@...sta.com>,
linux-kernel@...r.kernel.org
Subject: Killable stat/readdir
On Wed, Apr 16, 2008 at 02:50:34PM +0200, Andi Kleen wrote:
> killable stat and readdir would be even more important I would say.
>
> When sync/fsync takes too long it's typically just a kernel bug
> of some sort (like that long running MM starvation issue that stalls
> writes on some kinds of background activity) that should be really just
> fixed.
>
> But handling down network servers which hit stat/readdir etc. is
> a real situation not explained by a bug.
>
> For example a standard situation that hits me regularly is that
> I save something in firefox on a different server and then later
> turn that machine off. Then next time I try to save something
> in firefox it first blocks forever in stat()ing that down directory.
I think that's fixed now. Can you check with 2.6.25-rc1 or later?
If it's unkillable, can you let me know the wchan for that process?
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
--
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/
Powered by blists - more mailing lists