From: hpa@zytor.com (H. Peter Anvin)
To: linux-kernel@vger.kernel.org
Subject: Re: wrong hardlink count for /proc/PID directories
Date: Thu, 30 Dec 2004 01:12:11 +0000 (UTC) [thread overview]
Message-ID: <cqvklb$70t$1@terminus.zytor.com> (raw)
In-Reply-To: Pine.LNX.4.61.0412222340540.475@yvahk01.tjqt.qr
Followup to: <Pine.LNX.4.61.0412222340540.475@yvahk01.tjqt.qr>
By author: Jan Engelhardt <jengelh@linux01.gwdg.de>
In newsgroup: linux.dev.kernel
>
> You could try working around this by using -noleaf. (Which is by no means a
> solution.)
>
> Hm, I have 2.6.8+.9-rc2, and /proc/1 for example has a link count of 3 which
> seems reasonable: ".", "fd" and "task".
>
You're missing "attr", and you're not counting the directory entry
from below.
directory + "." + "attr/.." + "fd/.." + "task/.." = 5.
It should either return the correct value or set it to 1.
-hpa
prev parent reply other threads:[~2004-12-30 1:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-22 22:16 wrong hardlink count for /proc/PID directories Egmont Koblinger
2004-12-22 22:42 ` Jan Engelhardt
2004-12-22 23:02 ` Egmont Koblinger
2004-12-30 1:12 ` H. Peter Anvin [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='cqvklb$70t$1@terminus.zytor.com' \
--to=hpa@zytor.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