Vivek Goyal <[email protected]> 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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |