Re: [PATCH] print_dev_t for 2.6.0-test1-mm

From: Roman Zippel (zippel@linux-m68k.org)
Date: Thu Jul 17 2003 - 03:47:08 EST


Hi,

On Thu, 17 Jul 2003, Joel Becker wrote:

> On Wed, Jul 16, 2003 at 04:49:17PM -0700, Andrew Morton wrote:
> > Please describe a scenario in which a filesystem which works on current
> > kernels will, in a 64-bit-dev_t kernel, call init_special_inode() with a
> > 16:16 encoded device number.
>
> Perhaps he's thinking of NFSv2. If you want to make a device
> bigger than 8:8... Personally, I'm happy to ignore NFSv2 for this.

It's not just NFS2, with NFS3 and later it also depends on how many and
which bits the server keeps. They usually use the standard major/minor/
makedev macros, so you only get back what the platform supports.
Splitting dev_t in major/minor numbers can be lots of fun...

bye, Roman

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



This archive was generated by hypermail 2b29 : Wed Jul 23 2003 - 22:00:28 EST