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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 10 Apr 2009 00:24:56 -0500
From:	Kumar Gala <galak@...nel.crashing.org>
To:	Sukadev Bhattiprolu <sukadev@...ux.vnet.ibm.com>
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?)


On Apr 9, 2009, at 8:03 PM, Sukadev Bhattiprolu wrote:

>>
>> -bash-3.2# ps
>> PID TTY          TIME CMD
>> 2289 ttyS0    00:00:00 bash
>> 2310 ttyS0    00:00:00 runltp
>> 2412 ttyS0    00:00:00 pan
>> 2448 ttyS0    00:00:00 recv01 <defunct>
>> 2450 ttyS0    00:00:00 recvfrom01 <defunct>
>> 2452 ttyS0    00:00:00 recvmsg01 <defunct>
>> 2473 ttyS0    00:00:00 rename14
>> 2474 ttyS0    00:00:01 rename14
>> 2477 ttyS0    00:00:00 rename14
>> 2481 ttyS0    00:00:00 ps
>> -bash-3.2# cat /proc/1/status
>> Name:   init
>> State:  T (stopped)
>
> init is in the stopped state.  Can you run "kill -CONT 1" ?

yes

>> Tgid:   1
>> Pid:    1
>> PPid:   0
>> TracerPid:      0
>> Uid:    0       0       0       0
>> Gid:    0       0       0       0
>> FDSize: 32
>> Groups:
>> VmPeak:     1948 kB
>> VmSize:     1944 kB
>> VmLck:         0 kB
>> VmHWM:       648 kB
>> VmRSS:       648 kB
>> VmData:      164 kB
>> VmStk:        84 kB
>> VmExe:       288 kB
>> VmLib:      1124 kB
>> VmPTE:        20 kB
>> Threads:        1
>> SigQ:   8/16384
>> SigPnd: 0000000000000000
>> ShdPnd: 0000000000010000
>
> Init does have the pending SIGCHLD, so the zombies should go away
> when init gets the SIGCONT.

That seems to clear it up.. But why has the behavior changed?  I  
didn't have to do the "kill -CONT 1" on 2.6.29.

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ