From: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: oleg@redhat.com,
linux-kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: LTP 20080131 causes defunct processes w/2.6.30-rc1 (possible ptrace issue?)
Date: Thu, 9 Apr 2009 14:39:10 -0700 [thread overview]
Message-ID: <20090409213910.GB30645@us.ibm.com> (raw)
In-Reply-To: <0D6A6388-C12F-4066-84B8-155381D14504@kernel.crashing.org>
Kumar Gala [galak@kernel.crashing.org] wrote:
>
> On Apr 9, 2009, at 2:49 PM, Sukadev Bhattiprolu wrote:
>
>> Kumar Gala [galak@kernel.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
next prev parent reply other threads:[~2009-04-09 21:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 15:43 Kumar Gala
2009-04-09 16:41 ` Kumar Gala
2009-04-09 19:49 ` Sukadev Bhattiprolu
2009-04-09 20:28 ` Kumar Gala
2009-04-09 21:39 ` Sukadev Bhattiprolu [this message]
2009-04-10 0:01 ` Kumar Gala
2009-04-10 1:03 ` Sukadev Bhattiprolu
2009-04-10 5:24 ` Kumar Gala
2009-04-10 12:15 ` Oleg Nesterov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090409213910.GB30645@us.ibm.com \
--to=sukadev@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=galak@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome