Date: Thu, 22 Sep 2005 00:46:48 -0700
From: Andrew Morton <akpm@osdl.org>
To: vgoyal@in.ibm.com
Cc: ebiederm@xmission.com, anderson@redhat.com, fastboot@lists.osdl.org,
       linux-kernel@vger.kernel.org
Subject: Re: [Fastboot] [PATCH] Kdump(x86): add note type NT_KDUMPINFO to
 kernel core dumps
Message-Id: <20050922004648.07a4147f.akpm@osdl.org>
In-Reply-To: <20050922073914.GA3753@in.ibm.com>
References: <20050921065633.GC3780@in.ibm.com>
	<m1mzm6ebqn.fsf@ebiederm.dsl.xmission.com>
	<20050922073914.GA3753@in.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1034
Lines: 25

Vivek Goyal <vgoyal@in.ibm.com> wrote:
>
> > - Why do you avoid storing the current task on the other cpus?
>  > 
>  > - Can't we derive the current task from the existing register information
>  >   already captured.  
> 
>  It can be done but as Dave suggested but that requires significant amount 
>  of job to be done as one has to traverse through the active task stacks and
>  look for crash_kexec(). An easier/simpler way is that kernel itself can 
>  report it.  Netdump, diskdump already do it. I think for simplicity, it 
>  makes sense to export this information from kernel in the form of note.
> 
>  Only issue I could think of is stack overflow and current might be 
>  corrupted after panic.
> 

Yes, traversing the task_structs in a crashed kernel sounds like a poor
idea.

-
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/