From: Al Viro <viro@ftp.linux.org.uk>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 8/8] fix handling of st_nlink on procfs root
Date: Wed, 15 Feb 2006 10:39:11 +0000 [thread overview]
Message-ID: <20060215103911.GL27946@ftp.linux.org.uk> (raw)
In-Reply-To: <m1slql3rn2.fsf@ebiederm.dsl.xmission.com>
On Wed, Feb 15, 2006 at 02:20:17AM -0700, Eric W. Biederman wrote:
> And it is actually wrong. It fails to take into account the static
> /proc entries.
> > + stat->nlink = proc_root.nlink + nr_processes();
The hell it does. See ^^^^^^^^^^^^^^ this.
next prev parent reply other threads:[~2006-02-15 10:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 20:31 [PATCH 8/8] fix handling of st_nlink on procfs root Al Viro
2006-02-09 1:04 ` Eric W. Biederman
2006-02-09 2:17 ` Al Viro
2006-02-09 3:14 ` Eric W. Biederman
2006-02-15 9:20 ` Eric W. Biederman
2006-02-15 10:39 ` Al Viro [this message]
2006-02-15 17:35 ` Eric W. Biederman
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=20060215103911.GL27946@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=ebiederm@xmission.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.