Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 16 Feb 2003 14:09:10 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 16 Feb 2003 14:09:10 -0500 Received: from dbl.q-ag.de ([80.146.160.66]:12735 "EHLO dbl.q-ag.de") by vger.kernel.org with ESMTP id ; Sun, 16 Feb 2003 14:09:10 -0500 Message-ID: <3E4FE416.5040604@colorfullife.com> Date: Sun, 16 Feb 2003 20:18:46 +0100 From: Manfred Spraul User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021202 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Martin J. Bligh" CC: Linus Torvalds , Anton Blanchard , Andrew Morton , Kernel Mailing List , Zwane Mwaikambo Subject: Re: Fw: 2.5.61 oops running SDET References: <26480000.1045422382@[10.10.2.4]> In-Reply-To: <26480000.1045422382@[10.10.2.4]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 720 Lines: 20 Martin J. Bligh wrote: >Well, I did the stupid safe thing, and it hangs the box once we get up to >a load of 32 with SDET. Below is what I did, the only other issue I can >see in here is that task_mem takes mm->mmap_sem which is now nested inside >the task_lock inside tasklist_lock ... but I can't see anywhere that's a >problem from a quick search > > task_lock is actually &spin_lock(tsk->alloc_lock); mmap_sem is a semaphore. Nesting means deadlock. -- Manfred - 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/