Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756411AbYAFAUm (ORCPT ); Sat, 5 Jan 2008 19:20:42 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753354AbYAFAUe (ORCPT ); Sat, 5 Jan 2008 19:20:34 -0500 Received: from ns2.g-housing.de ([81.169.133.75]:46444 "EHLO mail.g-house.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753317AbYAFAUe (ORCPT ); Sat, 5 Jan 2008 19:20:34 -0500 Date: Sun, 6 Jan 2008 01:20:17 +0100 (CET) From: Christian Kujau X-X-Sender: evil@sheep.housecafe.de To: Davide Libenzi cc: Peter Zijlstra , Herbert Xu , Ingo Molnar , "Rafael J. Wysocki" , Linux Kernel Mailing List , jfs-discussion@lists.sourceforge.net, Johannes Berg , Oleg Nesterov Subject: Re: 2.6.24-rc6: possible recursive locking detected In-Reply-To: Message-ID: References: <200801040006.47979.rjw@sisk.pl> <20080104083049.GC22803@elte.hu> <20080105071205.GA28936@gondor.apana.org.au> <1199552016.31975.41.camel@lappy> <1199552476.31975.45.camel@lappy> User-Agent: Alpine 0.999999 (DEB 847 2007-12-06) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 832 Lines: 21 On Sat, 5 Jan 2008, Davide Libenzi wrote: > A solution may be to move the call to ep_poll_safewake() (that'd become a > simple wake_up()) inside a tasklet or whatever is today trendy for delayed > work. But his kinda scares me to be honest, since epoll has already a > bunch of places where it could be asynchronously hit (plus performance > regression will need to be verified). Although I'm not able to reproduce this one right now, I'm happy to test any patches you guys come up with. Thanks for your time, Christian. -- BOFH excuse #78: Yes, yes, its called a design limitation -- 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/