Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751155AbXJVV3p (ORCPT ); Mon, 22 Oct 2007 17:29:45 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751166AbXJVV3i (ORCPT ); Mon, 22 Oct 2007 17:29:38 -0400 Received: from mx1.redhat.com ([66.187.233.31]:41461 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751149AbXJVV3h (ORCPT ); Mon, 22 Oct 2007 17:29:37 -0400 Date: Mon, 22 Oct 2007 17:29:26 -0400 From: Rik van Riel To: Miklos Szeredi Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org, xemul@openvz.org, Ian Kent Subject: Re: futex strangeness in 2.6.23-mm1/UML Message-ID: <20071022172926.03ca122a@bree.surriel.com> In-Reply-To: References: <20071022145321.195d929b@bree.surriel.com> Organization: Red Hat, Inc. X-Mailer: Claws Mail 2.9.1 (GTK+ 2.10.4; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1665 Lines: 47 On Mon, 22 Oct 2007 22:48:51 +0200 Miklos Szeredi wrote: > > > I'm getting a process stuck in pthread_rwlock_wrlock(), even > > > though it looks like the lock is not held by anybody. > > > > > > I think the last -mm was OK. Any ideas? > > > > > > If not, I'll go searching for the offending patch. > > > > I wonder if that's the same bug that's breaking autofs for me. > > Probably. > > > Oct 22 14:39:01 kenny automount[2299]: cache_readlock: mapent cache > > rwlock lock failed > > Oct 22 14:39:01 kenny automount[2299]: unexpected pthreads error: > > 11 at 65 in cache.c > > > > I'm bisecting 2.6.23-mm1 today to find the problem patch, with > > some luck I'll have it this afternoon. > > > > With the series applied up to > > whitespace-fixes-task-exit-handling.patch things work. > > > > It breaks before kswapd-should-only-wait-on-io-if-there-is-io.patch > > > > That leaves only about 60-80 patches to look at :) > > OK, the first patch that breaks something for me is: > > pid-namespaces-move-alloc_pid-lower-in-copy_process.patch Confirmed. That same patch is the point where the bisect here starts breaking autofs. Ian, it looks like the autofs code is innocent :) -- "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian W. Kernighan - 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/