Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 20 Feb 2003 13:53:31 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 20 Feb 2003 13:53:31 -0500 Received: from mx1.elte.hu ([157.181.1.137]:24214 "HELO mx1.elte.hu") by vger.kernel.org with SMTP id ; Thu, 20 Feb 2003 13:53:29 -0500 Date: Thu, 20 Feb 2003 20:00:26 +0100 (CET) From: Ingo Molnar Reply-To: Ingo Molnar To: Linus Torvalds Cc: Zwane Mwaikambo , Chris Wedgwood , Kernel Mailing List , "Martin J. Bligh" , William Lee Irwin III Subject: Re: doublefault debugging (was Re: Linux v2.5.62 --- spontaneous reboots) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1204 Lines: 36 On Thu, 20 Feb 2003, Linus Torvalds wrote: > > a true heisenbug. I cannot reproduce it anymore. Anyway, from the serial > > console i collected 3 instances of crashes - whatever it's worth. > > Pretty much every single time, release_task() has been there on the > backtrace. > > In fact, I bet you this code in do_exit() is the cause: > > preempt_disable(); > > if (tsk->exit_signal == -1) > *** release_task(tsk); *** > > schedule(); > > Note how "release_task()" will be releasing the stack that the process > is running on right now. [...] but, release_task() is a delayed thing for exactly this reason. It fills out the per-CPU task_cache but does not free the task. the release_task() + schedule() must be atomic though - ie. we must not be preempted anytime inbetween [because that other task could free the task_cache] - but i wasnt running with CONFIG_PREEMPT, so i cannot see how it could happen. Ingo - 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/