From: Jamie Lokier <lk@tantalophile.demon.co.uk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Paul Larson <plars@austin.ibm.com>,
Hubertus Franke <frankeh@us.ibm.com>,
Rik van Riel <riel@conectiva.com.br>,
Andries Brouwer <aebr@win.tue.nl>,
Andrew Morton <akpm@zip.com.au>,
andrea@suse.de, Dave Jones <davej@suse.de>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Linux-2.5 fix/improve get_pid()
Date: Sun, 11 Aug 2002 21:10:24 +0100 [thread overview]
Message-ID: <20020811211024.C3206@kushida.apsleyroad.org> (raw)
In-Reply-To: <1029101038.16424.74.camel@irongate.swansea.linux.org.uk>; from alan@lxorguk.ukuu.org.uk on Sun, Aug 11, 2002 at 10:23:58PM +0100
Alan Cox wrote:
> > So, in general, the way to detect hard links requires both objects to be
> > open at the same time? I was sure it was enough to stat(), and check
> > (st1.st_ino == st2.st_ino && st1.st_dev == st2.st_dev).
> >
> > Admittedly, one of the object could be renamed or deleted in that time
> > so it's not 100% reliable on changing filesystems.
>
> Hence you need both open at the same time.
... unless you know that what you're looking at isn't changing, or you
only guarantee correct results for parts of the filesystem which don't
change (`tar', `find' etc.)
Again, /proc is exempt! :)
-- Jamie
next prev parent reply other threads:[~2002-08-11 20:08 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-08 21:43 Hubertus Franke
2002-08-08 22:02 ` Linus Torvalds
2002-08-08 22:26 ` Linus Torvalds
2002-08-08 23:09 ` Albert D. Cahalan
2002-08-09 3:26 ` Chris Adams
2002-08-09 7:04 ` Albert D. Cahalan
2002-08-09 8:48 ` Helge Hafting
2002-08-09 10:32 ` Alan Cox
2002-08-09 9:35 ` Andrew Morton
2002-08-09 10:37 ` Andries Brouwer
2002-08-09 13:00 ` Chris Adams
2002-08-09 14:39 ` Albert D. Cahalan
2002-08-09 13:59 ` Rik van Riel
2002-08-09 14:57 ` Albert D. Cahalan
2002-08-08 22:34 ` Paul Larson
2002-08-08 22:44 ` Rik van Riel
2002-08-08 22:37 ` Rik van Riel
2002-08-09 1:49 ` Andries Brouwer
2002-08-09 19:34 ` Paul Larson
2002-08-09 20:13 ` Paul Larson
2002-08-09 20:40 ` Andries Brouwer
2002-08-09 21:23 ` Linus Torvalds
2002-08-09 21:42 ` Linus Torvalds
2002-08-09 21:46 ` Paul Larson
2002-08-09 22:04 ` Linus Torvalds
2002-08-10 17:23 ` Jamie Lokier
2002-08-10 18:33 ` Linus Torvalds
2002-08-10 18:48 ` Jamie Lokier
2002-08-11 20:41 ` Alan Cox
2002-08-11 19:58 ` Jamie Lokier
2002-08-11 21:23 ` Alan Cox
2002-08-11 20:10 ` Jamie Lokier [this message]
2002-08-12 8:56 ` Padraig Brady
2002-08-12 10:37 ` Alan Cox
2002-08-12 9:21 ` Padraig Brady
2002-08-12 14:40 ` Paul Larson
-- strict thread matches above, loose matches on Subject: below --
2002-08-12 16:15 Jim Houston
2002-08-09 0:53 Hubertus Franke
2002-08-08 21:50 Hubertus Franke
2002-08-08 18:56 Hubertus Franke
2002-08-08 19:15 ` Rik van Riel
2002-08-08 19:18 ` Paul Larson
2002-08-07 22:03 Paul Larson
2002-08-07 23:06 ` Andrew Morton
2002-08-08 0:24 ` Andries Brouwer
2002-08-08 19:42 ` William Lee Irwin III
2002-08-08 20:47 ` Andries Brouwer
2002-08-08 20:24 ` Linus Torvalds
2002-08-08 21:30 ` H. Peter Anvin
2002-08-08 21:45 ` William Lee Irwin III
2002-08-09 4:42 ` William Lee Irwin III
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=20020811211024.C3206@kushida.apsleyroad.org \
--to=lk@tantalophile.demon.co.uk \
--cc=aebr@win.tue.nl \
--cc=akpm@zip.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrea@suse.de \
--cc=davej@suse.de \
--cc=frankeh@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=plars@austin.ibm.com \
--cc=riel@conectiva.com.br \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®