Messages in this thread | ![/](/images/icornerl.gif) | | Date | Mon, 21 Apr 2003 21:16:50 +0200 | From | Jörn Engel <> | Subject | Re: [PATCH] new system call mknod64 |
| |
On Mon, 21 April 2003 19:54:24 +0100, viro@parcelfarce.linux.theplanet.co.uk wrote: > On Mon, Apr 21, 2003 at 11:35:31AM -0700, Linus Torvalds wrote: > > > > Since they are always in canonical format, there is no way for them to > > have the aliasing issue. However, even then they _should_ be careful, > > since it would be very confusing (and bad) if they consider > > > > 0x00010100 (major 1, minor 256) > > > > to be fundamentally different from > > > > 0x01ff (major 1, minor 255) > > > > and cause problems that way. > > > > In other words, if I'm a device driver, and I say that I want "range > > 0-0xfff" for "major 2", then I had better get _all_ of it. > > Sure. However, note that right now there is only one driver that > wants a range bigger than 256 (and has to split it). UNIX 98 ptys.
Once this whole matter has settled down a little, mtdchar might want more than 256 as well. The good news though, is that the old range should stay unchanged for compatibility and the more-than-256 range can remain unsplit.
Jörn
-- Simplicity is prerequisite for reliability. -- Edsger W. Dijkstra - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| ![\](/images/icornerr.gif) |