From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: "Pavel Emelyanov" <xemul@openvz.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: find: WARNING: Hard link count is wrong for /proc/1
Date: Mon, 2 Jun 2008 09:03:19 +0200 [thread overview]
Message-ID: <19f34abd0806020003ub40def1w9dc011a357367f02@mail.gmail.com> (raw)
In-Reply-To: <19f34abd0806020000h407e3fb1kadff228a3cf4c6f@mail.gmail.com>
On Mon, Jun 2, 2008 at 9:00 AM, Vegard Nossum <vegard.nossum@gmail.com> wrote:
...
> Will this do? (Untested)
>
> Vegard
>
>
> From a43ef05a8c1f8d45ca88e00fdd31c00ddfdba1b8 Mon Sep 17 00:00:00 2001
> From: Vegard Nossum <vegard.nossum@gmail.com>
> Date: Mon, 2 Jun 2008 08:57:45 +0200
> Subject: [PATCH] proc: fix /proc/<pid> link count
>
> commit e9720acd728a46cb40daa52c99a979f7c4ff195c
> Author: Pavel Emelyanov <xemul@openvz.org>
> Date: Fri Mar 7 11:08:40 2008 -0800
>
> [NET]: Make /proc/net a symlink on /proc/self/net (v3)
>
> introduced /proc/net without bumping the link count on /proc/self.
Oops ---^
Should say /proc/self/net. Sorry for the spamming.
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
next prev parent reply other threads:[~2008-06-02 7:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-02 6:31 Vegard Nossum
2008-06-02 7:00 ` Vegard Nossum
2008-06-02 7:03 ` Vegard Nossum [this message]
2008-06-02 15:53 ` Jan Kara
2008-06-02 16:11 ` Pekka Enberg
2008-06-02 16:14 ` Pekka Enberg
2008-06-03 1:59 ` Eric W. Biederman
2008-06-03 2:10 ` Andrew Morton
[not found] ` <m1fxrv18q2.fsf@x61.ebiederm.org>
2008-06-03 4:06 ` Vegard Nossum
2008-06-02 22:29 ` Rafael C. de Almeida
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=19f34abd0806020003ub40def1w9dc011a357367f02@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xemul@openvz.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®