From: Robert Love <rml@tech9.net>
To: Nick LeRoy <nleroy@cs.wisc.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Detecting threads vs processes with ps or /proc
Date: 08 Dec 2002 22:47:59 -0500 [thread overview]
Message-ID: <1039405679.14167.19.camel@phantasy> (raw)
In-Reply-To: <200212090319.gB93J7p20606@schroeder.cs.wisc.edu>
On Sun, 2002-12-08 at 22:18, Nick LeRoy wrote:
> Yeah, I thought of that, too. Probably not too likely, of course, but it
> still there. Murphy rules.
>
> Robert: Any thoughts on this?
Sure, it can happen. The original poster asked me this in private the
other day. The race is pretty improbable but it certainly can happen.
The heuristic is imperfect. Then again, this same sort of thing can
occur in other places too since all the reads in /proc are non-atomic
wrt each other.
Robert Love
next prev parent reply other threads:[~2002-12-09 3:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-09 0:24 Detecting threads vs processes with ps or /proc Albert D. Cahalan
2002-12-09 3:18 ` Nick LeRoy
2002-12-09 3:47 ` Robert Love [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-06 15:24 Nick LeRoy
2002-12-06 19:48 ` Robert Love
2002-12-06 19:56 ` Nick LeRoy
2002-12-06 20:09 ` Robert Love
2002-12-09 16:27 ` Jeremy Fitzhardinge
2002-12-08 12:24 ` Gilad Ben-Yossef
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=1039405679.14167.19.camel@phantasy \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nleroy@cs.wisc.edu \
/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