kexec: set prstatus.pr_pid to cpu id when current->pid is 0
in [Kernel]
|
Prev: [PATCH] [Bug 16494] NFS client over TCP hangs due to packet loss
Next: cgroup : add clone_children control file
From: Eric W. Biederman on 3 Aug 2010 04:20 Hui Zhu <teawater(a)gmail.com> writes: > On Tue, Aug 3, 2010 at 15:37, Eric W. Biederman <ebiederm(a)xmission.com> wrote: >> Hui Zhu <teawater(a)gmail.com> writes: >> > > Equal 0 is not a bug, the trouble is a lot of core's pid is same. > > This is what gdb say: > /* Found an old thread with the same id. It has to be dead, > otherwise we wouldn't be adding a new thread with the same id. > The OS is reusing this id --- delete it, and recreate a new > one. */ gdb bug compatibility is not a primary goal. Having an extensible format and not inventing it totally out of the blue is the goal. The goal was always that something could post process the output of the kernel crashdump and create something that is gdb compatible. It looks to me like it would take just a moment to strip out all of the idle threads. Claiming the pid is the cpu number when the pid is the idle pid gives you no insulation against duplication, and it looses information. Eric -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |