mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andries.Brouwer@cwi.nl
To: Andries.Brouwer@cwi.nl, torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kill i_dev
Date: Fri, 22 Nov 2002 02:34:35 +0100 (MET)	[thread overview]
Message-ID: <UTC200211220134.gAM1YZn19628.aeb@smtp.cwi.nl> (raw)

    From torvalds@transmeta.com  Fri Nov 22 00:57:03 2002

    > 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?

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 numbers (in user space) to a valid thing, so that they wouldn't just
    be random numbers.

I don't know. We can try in-kernel to give these well-known services
well-known numbers. Or we can give them essentially random
numbers like today but publish these somewhere, e.g. under /sys.
Both are easy, but seem too heavy for a value used by nobody.
We have process IDs and anonymous fs IDs, and both are just what
they happen to be.


Andries


[If userspace wants to know the present value, then create a socket,
stat, 3! Create a pipe, stat, 7!]

             reply	other threads:[~2002-11-22  1:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-22  1:34 Andries.Brouwer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-21 23:46 Andries.Brouwer
2002-11-21 23:56 ` Linus Torvalds
2002-11-22  0:22   ` H. Peter Anvin
2002-11-22  1:18   ` Christoph Hellwig

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=UTC200211220134.gAM1YZn19628.aeb@smtp.cwi.nl \
    --to=andries.brouwer@cwi.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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®