From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kill i_dev
Date: 21 Nov 2002 16:22:54 -0800 [thread overview]
Message-ID: <arjtcu$8q3$1@cesium.transmeta.com> (raw)
In-Reply-To: Pine.LNX.4.44.0211211548530.5779-100000@penguin.transmeta.com
Followup to: <Pine.LNX.4.44.0211211548530.5779-100000@penguin.transmeta.com>
By author: Linus Torvalds <torvalds@transmeta.com>
In newsgroup: linux.dev.kernel
>
> Applied.
>
> > There is a single side effect: a stat on a socket now sees
> > a nonzero st_dev. There is nothing against that - FreeBSD
> > has a nonzero value as well - but there is at least one
> > utility (fuser) that will need an update.
>
> Looking at the patch (not testing it), as far as I can tell we'll return a
> basically random number that is just whatever the anonymous super-block
> was allocated, right?
>
> I'm not convinced that returning random numbers to user space is
> necessarily a great idea.. That said, I think we already do it for unnamed
> pipes anyway, so I'm more wondering if we should have some way to map
> these numbews (in user space) to a valid thing, so that they wouldn't just
> be random numbers.
>
What's really important is that they don't map to anything else. I
don't think it matters what the numbers is, since there is a much
better way to find out that you're a pipe or a socket.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2002-11-22 0:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-21 23:46 [PATCH] kill i_dev Andries.Brouwer
2002-11-21 23:56 ` Linus Torvalds
2002-11-22 0:22 ` H. Peter Anvin [this message]
2002-11-22 1:18 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2002-11-22 1:34 Andries.Brouwer
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='arjtcu$8q3$1@cesium.transmeta.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 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.