From: William Lee Irwin III <wli@holomorphy.com>
To: Andrew Volkov <Andrew.Volkov@transas.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: possible proceses leak
Date: Mon, 8 Dec 2003 10:51:21 -0800 [thread overview]
Message-ID: <20031208185121.GM8039@holomorphy.com> (raw)
In-Reply-To: <2E74F312D6980D459F3A05492BA40F8D0391B0EE@clue.transas.com>
On Mon, Dec 08, 2003 at 09:45:17PM +0300, Andrew Volkov wrote:
> Yes.
> And same bug in kernel/sched.c in ALL *_sleep_on
> Andrey
Heh, no wonder everyone wants to get rid of the things.
-- wli
next prev parent reply other threads:[~2003-12-08 18:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-08 18:45 PROBLEM: possible proceses leak Andrew Volkov
2003-12-08 18:51 ` William Lee Irwin III [this message]
2003-12-08 19:09 ` Linus Torvalds
2003-12-08 19:23 ` William Lee Irwin III
-- strict thread matches above, loose matches on Subject: below --
2003-12-08 19:34 Andrew Volkov
2003-12-08 18:01 Andrew Volkov
2003-12-08 18:25 ` William Lee Irwin III
2003-12-08 19:08 ` Linus Torvalds
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=20031208185121.GM8039@holomorphy.com \
--to=wli@holomorphy.com \
--cc=Andrew.Volkov@transas.com \
--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;
as well as URLs for NNTP newsgroup(s).