Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753745AbXJWBMA (ORCPT ); Mon, 22 Oct 2007 21:12:00 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751412AbXJWBLy (ORCPT ); Mon, 22 Oct 2007 21:11:54 -0400 Received: from mx1.redhat.com ([66.187.233.31]:34930 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751339AbXJWBLx (ORCPT ); Mon, 22 Oct 2007 21:11:53 -0400 Date: Mon, 22 Oct 2007 21:11:43 -0400 From: Rik van Riel To: Andrew Morton Cc: miklos@szeredi.hu, linux-kernel@vger.kernel.org, xemul@openvz.org, raven@themaw.net Subject: Re: futex strangeness in 2.6.23-mm1/UML Message-ID: <20071022211143.5f69d790@bree.surriel.com> In-Reply-To: <20071022171624.0c00f8da.akpm@linux-foundation.org> References: <20071022145321.195d929b@bree.surriel.com> <20071022172926.03ca122a@bree.surriel.com> <20071022200742.6f3acbb2@bree.surriel.com> <20071022171624.0c00f8da.akpm@linux-foundation.org> 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: 1377 Lines: 34 On Mon, 22 Oct 2007 17:16:24 -0700 Andrew Morton wrote: > > > > > 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 guess we can debug it in the old-fashioned ways. The first of > which is to palm the problem off on Pavel ;) > > I don't recall seeing a simple step-by-step way by which others can > reproduce this? I have my systems set up to automount my home directory over NFS when I log in. When trying to log in to the system with 2.6.23-mm1, I get the messages from above in my syslog, and the NFS filesystem is not automounted. I am thinking something in autofs or the pid-namespace* patches does not match up and uses a wrong PID number or process pointer when trying to lock things. Which code is at fault I have no idea... -- "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/