All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@caldera.de>
To: linux-lvm@sistina.com
Cc: Alexander Viro <viro@math.psu.edu>,
	Linus Torvalds <torvalds@transmeta.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [linux-lvm] Re: [RFLART] kdev_t in ioctls
Date: Mon Jan 14 12:14:02 2002	[thread overview]
Message-ID: <20020114191342.A3731@caldera.de> (raw)
In-Reply-To: <20020114190834.A3473@caldera.de>; from hch@caldera.de on Mon, Jan 14, 2002 at 07:08:34PM +0100

On Mon, Jan 14, 2002 at 07:08:34PM +0100, Christoph Hellwig wrote:
> > The good news is that the bit-for-bit representation of old kdev_t and
> > "dev_t" are obviously 100% the same, so we should just make the damn thing
> > be dev_t, and user land will never notice anything.
> 
> Glibc disagrees with you (bits/types.h):
> 
> typedef __u_quad_t __dev_t;             /* Type of device numbers.  */
> 
> We'd have to use __kernel_dev_t instead which again pulls kernel
> headers in..

Argg.  That's also non-funny:

[hch@sb linux]$ grep __kernel_dev_t; include/asm-*/posix_types.h
include/asm-alpha/posix_types.h:typedef unsigned int	__kernel_dev_t;
include/asm-arm/posix_types.h:typedef unsigned short	__kernel_dev_t;
include/asm-cris/posix_types.h:typedef unsigned short	__kernel_dev_t;
include/asm-i386/posix_types.h:typedef unsigned short	__kernel_dev_t;
include/asm-ia64/posix_types.h:typedef unsigned int	__kernel_dev_t;
include/asm-m68k/posix_types.h:typedef unsigned short	__kernel_dev_t;
include/asm-mips64/posix_types.h:typedef unsigned int	__kernel_dev_t;
include/asm-mips/posix_types.h:typedef unsigned int	__kernel_dev_t;
include/asm-parisc/posix_types.h:typedef unsigned int	__kernel_dev_t;
include/asm-ppc/posix_types.h:typedef unsigned int	__kernel_dev_t;
include/asm-s390/posix_types.h:typedef unsigned short	__kernel_dev_t;
include/asm-s390x/posix_types.h:typedef unsigned int	__kernel_dev_t;
include/asm-sh/posix_types.h:typedef unsigned short	__kernel_dev_t;
include/asm-sparc64/posix_types.h:typedef unsigned int	__kernel_dev_t;
include/asm-sparc/posix_types.h:typedef unsigned short	__kernel_dev_t;

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@caldera.de>
To: linux-lvm@sistina.com
Cc: Alexander Viro <viro@math.psu.edu>,
	Linus Torvalds <torvalds@transmeta.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [linux-lvm] Re: [RFLART] kdev_t in ioctls
Date: Mon, 14 Jan 2002 19:13:42 +0100	[thread overview]
Message-ID: <20020114191342.A3731@caldera.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0201140957040.15128-100000@penguin.transmeta.com> <20020114190834.A3473@caldera.de>
In-Reply-To: <20020114190834.A3473@caldera.de>; from hch@caldera.de on Mon, Jan 14, 2002 at 07:08:34PM +0100

On Mon, Jan 14, 2002 at 07:08:34PM +0100, Christoph Hellwig wrote:
> > The good news is that the bit-for-bit representation of old kdev_t and
> > "dev_t" are obviously 100% the same, so we should just make the damn thing
> > be dev_t, and user land will never notice anything.
> 
> Glibc disagrees with you (bits/types.h):
> 
> typedef __u_quad_t __dev_t;             /* Type of device numbers.  */
> 
> We'd have to use __kernel_dev_t instead which again pulls kernel
> headers in..

Argg.  That's also non-funny:

[hch@sb linux]$ grep __kernel_dev_t; include/asm-*/posix_types.h
include/asm-alpha/posix_types.h:typedef unsigned int	__kernel_dev_t;
include/asm-arm/posix_types.h:typedef unsigned short	__kernel_dev_t;
include/asm-cris/posix_types.h:typedef unsigned short	__kernel_dev_t;
include/asm-i386/posix_types.h:typedef unsigned short	__kernel_dev_t;
include/asm-ia64/posix_types.h:typedef unsigned int	__kernel_dev_t;
include/asm-m68k/posix_types.h:typedef unsigned short	__kernel_dev_t;
include/asm-mips64/posix_types.h:typedef unsigned int	__kernel_dev_t;
include/asm-mips/posix_types.h:typedef unsigned int	__kernel_dev_t;
include/asm-parisc/posix_types.h:typedef unsigned int	__kernel_dev_t;
include/asm-ppc/posix_types.h:typedef unsigned int	__kernel_dev_t;
include/asm-s390/posix_types.h:typedef unsigned short	__kernel_dev_t;
include/asm-s390x/posix_types.h:typedef unsigned int	__kernel_dev_t;
include/asm-sh/posix_types.h:typedef unsigned short	__kernel_dev_t;
include/asm-sparc64/posix_types.h:typedef unsigned int	__kernel_dev_t;
include/asm-sparc/posix_types.h:typedef unsigned short	__kernel_dev_t;


  reply	other threads:[~2002-01-14 12:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-14 17:56 [RFLART] kdev_t in ioctls Alexander Viro
2002-01-14 12:04 ` [linux-lvm] " Linus Torvalds
2002-01-14 18:01   ` Linus Torvalds
2002-01-13 17:17   ` [linux-lvm] " Joe Thornber
2002-01-15  6:27     ` Joe Thornber
2002-01-14 12:09   ` Christoph Hellwig
2002-01-14 18:08     ` Christoph Hellwig
2002-01-14 12:14     ` Christoph Hellwig [this message]
2002-01-14 18:13       ` Christoph Hellwig
2002-01-14 12:45       ` Alan Cox
2002-01-14 18:56         ` Alan Cox
2002-01-14 12:47         ` Christoph Hellwig
2002-01-14 18:45           ` Christoph Hellwig
2002-01-14 12:53           ` Linus Torvalds
2002-01-14 18:50             ` Linus Torvalds
2002-01-14 12:21   ` Alexander Viro
2002-01-14 18:20     ` Alexander Viro
  -- strict thread matches above, loose matches on Subject: below --
2002-01-15 14:46 [linux-lvm] " Andries.Brouwer
2002-01-15 20:44 ` Andries.Brouwer

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=20020114191342.A3731@caldera.de \
    --to=hch@caldera.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-lvm@sistina.com \
    --cc=torvalds@transmeta.com \
    --cc=viro@math.psu.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.