linux-kernel - Re: LTP 20080131 causes defunct processes w/2.6.30-rc1 (possible ptrace issue?)

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]

Message-Id: <0D6A6388-C12F-4066-84B8-155381D14504@kernel.crashing.org>
Date:	Thu, 9 Apr 2009 15:28:31 -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 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
TracerPid:      0
Uid:    0       0       0       0
Gid:    0       0       0       0
FDSize: 0
Groups: 0 1 2 3 4 6 10
Threads:        1
SigQ:   8/16384
SigPnd: 0000000000000000
ShdPnd: 0000000000004100
SigBlk: 0000000000000000
SigIgn: 0000000000000000
SigCgt: 0000000000000000
CapInh: 0000000000000000
CapPrm: fffffffffffffeff
CapEff: fffffffffffffeff
CapBnd: fffffffffffffeff
voluntary_ctxt_switches:        6
nonvoluntary_ctxt_switches:     0

If you have suggestion on how to dump the stack I can provide that as  
well.

> If the parent is 'init', is there anything special about the init on  
> your board
> or on the simulator - like are you running the tests in a container ?

Its an old init from fedora 3 or something like that.  Its not running  
in any special way (not container, no hypervisor, etc.)

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