From: Linus Torvalds <torvalds@transmeta.com>
To: viro@parcelfarce.linux.theplanet.co.uk
Cc: Christoph Hellwig <hch@infradead.org>,
Roman Zippel <zippel@linux-m68k.org>,
"David S. Miller" <davem@redhat.com>, <Andries.Brouwer@cwi.nl>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] new system call mknod64
Date: Mon, 21 Apr 2003 13:02:48 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0304211259120.17221-100000@home.transmeta.com> (raw)
In-Reply-To: <20030421193510.GQ10374@parcelfarce.linux.theplanet.co.uk>
On Mon, 21 Apr 2003 viro@parcelfarce.linux.theplanet.co.uk wrote:
>
> stat() family, ustat(2), quota syscall, ioctls that pass device numbers,
> /dev/raw, RAID, probably process accounting.
>
> FWIW, I believe that you are overestimating the amount of internal code
> that cares about device numbers.
I don't think so. I agree that it's not very many places, and in fact the
reason we currently do _not_ do dev_t replacement at system call boundary
is that it looks to be so rare that it's easier to always use the user
representation, and then always do the explicit MINOR/MAJOR in the places
that use dev_t.
I don't really care which way it is done (ie system call boundary or in
usage), and I'm happy with either - as long as it always _does_ get done,
and nobody ever uses the user representation that can have aliases for
anything important.
(My preference, quite frankly, is to always have major/minor be explicit,
and never deal with "dev_t" at all. Especially with a 64-bit dev_t it is
actually often _faster_ and _simpler_ to just carry major/minor around
explicitly because then gcc won't ever have to worry it's small deficient
brain about "unsigned long long".)
Linus
next prev parent reply other threads:[~2003-04-21 19:50 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-20 21:26 [PATCH] new system call mknod64 Andries.Brouwer
2003-04-20 21:43 ` David S. Miller
2003-04-20 21:56 ` Linus Torvalds
2003-04-21 11:59 ` Roman Zippel
2003-04-21 18:01 ` Linus Torvalds
2003-04-21 18:10 ` Christoph Hellwig
2003-04-21 18:21 ` viro
2003-04-21 18:22 ` Linus Torvalds
2003-04-21 18:27 ` viro
2003-04-21 18:35 ` Linus Torvalds
2003-04-21 18:54 ` viro
2003-04-21 19:16 ` Jörn Engel
2003-04-21 18:35 ` Christoph Hellwig
2003-04-21 18:42 ` H. Peter Anvin
2003-04-21 18:44 ` Linus Torvalds
2003-04-21 18:47 ` Christoph Hellwig
2003-04-21 18:58 ` viro
2003-04-21 19:05 ` Linus Torvalds
2003-04-21 19:35 ` viro
2003-04-21 20:02 ` Linus Torvalds [this message]
2003-04-21 19:04 ` Linus Torvalds
2003-04-21 19:59 ` H. Peter Anvin
2003-04-21 18:51 ` H. Peter Anvin
2003-04-21 23:49 ` Roman Zippel
[not found] <20030421215009$2052@gated-at.bofh.it>
[not found] ` <20030421231010$7ee3@gated-at.bofh.it>
[not found] ` <20030422000016$17e3@gated-at.bofh.it>
[not found] ` <20030422083014$0fe2@gated-at.bofh.it>
2003-04-22 20:02 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2003-04-22 1:02 Andries.Brouwer
2003-04-22 1:32 ` H. Peter Anvin
2003-04-22 2:01 ` Jamie Lokier
2003-04-22 2:52 ` H. Peter Anvin
2003-04-22 6:00 ` jw schultz
2003-04-22 17:17 ` H. Peter Anvin
2003-04-21 21:48 Andries.Brouwer
2003-04-21 22:07 ` Linus Torvalds
2003-04-21 21:43 Andries.Brouwer
2003-04-21 23:02 ` H. Peter Anvin
2003-04-21 23:50 ` Jamie Lokier
2003-04-22 8:24 ` Shachar Shemesh
2003-04-20 22:12 Andries.Brouwer
2003-04-21 6:31 ` H. Peter Anvin
2003-04-20 20:34 Andries.Brouwer
2003-04-20 21:12 ` David S. Miller
2003-04-20 18:39 Andries.Brouwer
2003-04-20 18:52 ` 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=Pine.LNX.4.44.0304211259120.17221-100000@home.transmeta.com \
--to=torvalds@transmeta.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=davem@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
--cc=zippel@linux-m68k.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;
as well as URLs for NNTP newsgroup(s).