mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Phil Howard <phil-linux-kernel@ipal.net>
To: kees <kees@schoen.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Q: straced processes don't go away
Date: Thu, 15 Nov 2001 07:32:57 -0600	[thread overview]
Message-ID: <20011115073257.A16769@vega.ipal.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0111150836290.20276-100000@schoen3.schoen.nl>
In-Reply-To: <Pine.LNX.4.33.0111150836290.20276-100000@schoen3.schoen.nl>

On Thu, Nov 15, 2001 at 08:39:30AM +0100, kees wrote:

| In my attempts to find the problem with the tun device I did
| a couple of strace sessions.
| 
| My processlist now shows a couple of unkillable (kill -KILL )
| processes:
| 
| 444     0 24239     1   9   0     0    0 do_exi RW   ?          0:00
| [vtund]
| 444     0 24305     1   8   0     0    0 do_exi RW   ?          0:00
| [vtund]
| 444     0 24880     1   9   0     0    0 do_exi RW   ?          0:00
| [vtund]
| 
| kernel 2.4.14 with 2.4.15-pre3 applied

I've been debugging some timer bugs in a daemon library I'm developing
and have been stracing it.  Among many things done are a variety of
kills, including -KILL, -INT, -TERM and -HUP, while being straced.
When I do the kill, I see strace output showing the events correctly
and in the case of -KILL the process definitely goes away.

This is with kernel 2.4.13.  So this is not a broad problem and may be
specific to states vtund is in, or changes since 2.4.13, or both.

-- 
-----------------------------------------------------------------
| Phil Howard - KA9WGN |   Dallas   | http://linuxhomepage.com/ |
| phil-nospam@ipal.net | Texas, USA | http://phil.ipal.org/     |
-----------------------------------------------------------------

      reply	other threads:[~2001-11-15 13:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-15  7:39 kees
2001-11-15 13:32 ` Phil Howard [this message]

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=20011115073257.A16769@vega.ipal.net \
    --to=phil-linux-kernel@ipal.net \
    --cc=kees@schoen.nl \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®