From: Arnd Bergmann <arnd@arndb.de>
To: "David S. Miller" <davem@redhat.com>
Subject: Re: ioctl cleanups: enable sg_io and serial stuff to be shared
Date: Thu, 8 May 2003 01:50:10 +0200
User-Agent: KMail/1.5.1
Cc: pavel@ucw.cz, hch@infradead.org, linux-kernel@vger.kernel.org
References: <20030507152856.GF412@elf.ucw.cz> <200305072113.07004.arnd@arndb.de> <20030507.111245.25138161.davem@redhat.com>
In-Reply-To: <20030507.111245.25138161.davem@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="euc-jp"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200305080150.10697.arnd@arndb.de>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 960
Lines: 23

On Wednesday 07 May 2003 20:12, David S. Miller wrote:
>    From: Arnd Bergmann <arnd@arndb.de>
>    Date: Wed, 7 May 2003 21:13:07 +0200
>
>    Btw: is there any bit in the ioctl number definition that can
>    be (ab)used for compat_ioctl?
>
> Unfortunately no.  All the bits are used in order to allow
> the size field of the encoding to be as large as possible.

I checked the numbers that are in arch/sparc64/kernel/ioctl32.o
and found none that uses more than 9 bits for the size field,
while every architecture has at least 13 bits space. There may
of course be other ioctls that can not live with 12 bit size
fields and it's probably a bad idea to require special-casing
these in the compat code.

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