| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 9 Apr 2009 14:39:10 -0700 From: Sukadev Bhattiprolu <sukadev@...ux.vnet.ibm.com> To: Kumar Gala <galak@...nel.crashing.org> Cc: oleg@...hat.com, linux-kernel Mailing List <linux-kernel@...r.kernel.org>, Andrew Morton <akpm@...ux-foundation.org> Subject: Re: LTP 20080131 causes defunct processes w/2.6.30-rc1 (possible ptrace issue?) Kumar Gala [galak@...nel.crashing.org] wrote: > > On Apr 9, 2009, at 2:49 PM, Sukadev Bhattiprolu wrote: > >> Kumar Gala [galak@...nel.crashing.org] wrote: >>> >>> On Apr 9, 2009, at 10:43 AM, Kumar Gala wrote: >>> >>>> I'm seeing some weird behavior in 2.6.30-rc1 that didn't exist in >>>> 2.6.29. >>>> We have a slightly older LTP version (20080131) that we run on some >>>> embedded PPC boards. If I run the syscall tests on 2.6.29 things pass >>>> as >> >> Will try to repro on a normal machine, but can you attach the >> /proc/pid/status >> (and possibly the stack) of the parent of the 'recv01' ? > > Name: recv01 > State: Z (zombie) > Tgid: 2449 > Pid: 2449 > PPid: 1 Ok, but I meant the status of the parent (i.e /proc/1/status in this case). To get the stack, if CONFIG_MAGIC_SYSRQ=y, you can: $ echo 1 > /proc/sys/kernel/sysrq $ echo t > /proc/sysrq-trigger $ dmesg > /tmp/dmesg.out Look in /tmp/dmesg.out for the process stack Suka -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists