linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Joel Becker <Joel.Becker@oracle.com>, Greg KH <greg@kroah.com>,
	Andries.Brouwer@cwi.nl, akpm@digeo.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] register_blkdev
Date: 08 Mar 2003 23:56:35 +0000	[thread overview]
Message-ID: <1047167794.26807.55.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0303081431030.19716-100000@home.transmeta.com>

On Sat, 2003-03-08 at 22:36, Linus Torvalds wrote:
> I certainly agree that we'll need to open up the number space, but I 
> really do think that the way to _manage_ it is something like what Greg 
> pointed to - dynamic tols with "rules" on allocation, instead of the 
> stupid static manual assignment thing.

Greg's tools still have unsolved security holes in them. We still have
unsolved persistence of permissions and reuse problems. I think they are
soluble. The current insoluble dirty great security hole we have is
lack of vhangup for non tty devices (ie BSD revoke). Right now that
allows some quite nasty things to occur if you ever had console access.

> We're pretty close to it already. I thought some Linux vendors are already 
> starting to pick up on the hotplugging tools, simply because there are no 
> real alternatives.

For certain kinds of device yes.

> And once you do it that way, the static numbers are meaningless. And good 
> riddance.

Static naming/permissions management is current simply the best of
available evils for many things. With stuff like modem arrays on serial
ports its also neccessary to know what goes where. I'm all for moving to
setups when possible where things like SCSI volumes carry a volume name
and permission/acl data in the label



  reply	other threads:[~2003-03-08 22:40 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-08  0:57 [PATCH] register_blkdev Andries.Brouwer
2003-03-08  0:53 ` Greg KH
     [not found]   ` <20030308073407.A24272@infradead.org>
2003-03-08 19:29     ` Greg KH
2003-03-08 19:43       ` Christoph Hellwig
2003-03-08 21:26         ` H. Peter Anvin
2003-03-08 21:55           ` Christoph Hellwig
2003-03-08 21:41         ` Joel Becker
2003-03-08 21:52           ` Christoph Hellwig
2003-03-08 22:16             ` Joel Becker
2003-03-08 22:21               ` Christoph Hellwig
2003-03-10 17:31                 ` Joel Becker
2003-03-08 23:37             ` Alan Cox
2003-03-08 22:36               ` Linus Torvalds
2003-03-08 23:56                 ` Alan Cox [this message]
2003-03-09  5:08             ` Gerrit Huizenga
2003-03-17 19:21           ` Steven Dake
  -- strict thread matches above, loose matches on Subject: below --
2003-03-08 20:59 Andries.Brouwer
2003-03-08 21:09 ` Christoph Hellwig
2003-03-08 20:26 Andries.Brouwer
2003-03-08 20:31 ` Christoph Hellwig
2003-03-08  1:49 Andries.Brouwer
2003-03-07 19:50 Andries.Brouwer
2003-03-07 19:52 ` Christoph Hellwig
2003-03-07 19:32 Andries.Brouwer
2003-03-07 19:36 ` Christoph Hellwig
2003-03-07 20:30   ` Andrew Morton
2003-03-07 22:12     ` Greg KH
2003-03-07 22:33       ` Andrew Morton
2003-03-07 23:45         ` Greg KH
2003-03-08  1:14           ` Alan Cox
2003-03-08  0:50             ` Greg KH
2003-03-08  1:05               ` Andrew Morton
2003-03-08  1:03                 ` Greg KH
2003-03-08  1:13                 ` Linus Torvalds
2003-03-08 15:09                   ` Alan Cox
2003-03-08 15:53                     ` Christoph Hellwig
2003-03-09  2:02                     ` Chris Wedgwood
2003-03-10  4:46                     ` Oliver Xymoron
2003-03-08 15:11               ` Alan Cox
2003-03-08 19:37                 ` Greg KH
2003-03-08 19:50                   ` Christoph Hellwig
2003-03-08 20:00                     ` Greg KH
2003-03-08 20:23                       ` Christoph Hellwig
2003-03-07 22:55       ` Joel Becker
2003-03-07 22:57         ` Christoph Hellwig
2003-03-07 23:17           ` Randy.Dunlap
2003-03-07 23:38             ` John Cherry
2003-03-07 23:36               ` Christoph Hellwig
2003-03-07 23:46                 ` Andrew Morton
2003-03-07 23:54                   ` Christoph Hellwig
2003-03-08  1:49                     ` Joel Becker
2003-03-08  1:58                       ` Greg KH
2003-03-08  2:15                         ` Joel Becker
2003-03-08  2:18                           ` Linus Torvalds
2003-03-08  2:42                             ` Joel Becker
2003-03-08 19:31                           ` Greg KH
2003-03-08 21:39                             ` Joel Becker
2003-03-08 21:59                               ` Greg KH
2003-03-08  1:04           ` Alan Cox
2003-03-09  4:32         ` Horst von Brand
2003-03-09  5:11           ` Valdis.Kletnieks
2003-03-07 18:49 Andries.Brouwer
2003-03-07 19:06 ` 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=1047167794.26807.55.camel@irongate.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=Joel.Becker@oracle.com \
    --cc=akpm@digeo.com \
    --cc=greg@kroah.com \
    --cc=hch@infradead.org \
    --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;
as well as URLs for NNTP newsgroup(s).