From: William Lee Irwin III <wli@holomorphy.com>
To: Albert Cahalan <albert@users.sf.net>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>,
Andrew Morton OSDL <akpm@osdl.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: fake_ino fixes
Date: Mon, 13 Sep 2004 19:03:55 -0700 [thread overview]
Message-ID: <20040914020355.GG9106@holomorphy.com> (raw)
In-Reply-To: <1095090739.2191.1465.camel@cube>
On Mon, Sep 13, 2004 at 11:52:19AM -0400, Albert Cahalan wrote:
> This improves /proc inode numbering a bit.
> If ino_t is 32-bit: just fix task 0 handling
> If ino_t is 64-bit: fix large fd numbers too
> Handling PID 0xffff on 32-bit was dropped in
> favor of handling PID 0 correctly, since PID 0
> can be seen with the default pid_max value.
Sounds like a good stopgap measure unless someone's already got a more
comprehensive sweep that enables larger pid spaces on 32-bit.
-- wli
prev parent reply other threads:[~2004-09-14 2:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-13 15:52 fake_ino fixes Albert Cahalan
2004-09-14 2:03 ` William Lee Irwin III [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=20040914020355.GG9106@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@osdl.org \
--cc=albert@users.sf.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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