From: Arnd Bergmann <arnd@arndb.de>
To: "David S. Miller" <davem@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
Gerd Knorr <kraxel@bytesex.org>
Cc: Pavel Machek <pavel@ucw.cz>, linux-kernel@vger.kernel.org
Subject: Re: ioctl cleanups: enable sg_io and serial stuff to be shared
Date: Thu, 8 May 2003 17:23:19 +0200 [thread overview]
Message-ID: <200305081723.19285.arnd@arndb.de> (raw)
In-Reply-To: <1052318339.9817.8.camel@rth.ninka.net>
Gerd Knorr wrote:
> ioctl struct size and the ioctl number (which has the size encoded)
> should end up being different too. Anyone aware of corner cases where
> this isn't going to work?
About half of the ioctls that need special care have fixed numbers
instead of using _IOR() etc, see e.g. include/linux/sockios.h,
or they get the definition wrong in some way.
The way you do it in your patch could work for many cases, but it
won't be enough to eliminate HANDLE_IOCTL(), if that is desired.
Adding fops->compat_ioctl() makes it possible to eventually replace
all HANDLE_IOCTL() and keep only COMPATIBLE_IOCTL(), which in turn
would become simpler to deal with.
If we don't add fops->compat_ioctl(), the ioctl handlers could
however look at (current_thread_info()->flags & _TIF_32BIT) to find
out if which user data structure they should expect. Is that reliable?
Do we already have a macro to do it?
Arnd <><
next prev parent reply other threads:[~2003-05-08 15:15 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030507104008$12ba@gated-at.bofh.it>
2003-05-07 11:51 ` ioctl cleanups: enable sg_io and serial stuff to be shared Arnd Bergmann
2003-05-07 12:41 ` Pavel Machek
2003-05-07 12:56 ` Christoph Hellwig
2003-05-07 14:39 ` David S. Miller
2003-05-07 15:12 ` Jeff Garzik
2003-05-07 14:07 ` David S. Miller
2003-05-08 10:46 ` Gerd Knorr
2003-05-08 15:16 ` Ben Collins
2003-05-08 15:51 ` Christoph Hellwig
2003-05-08 15:37 ` Ben Collins
2003-05-08 19:34 ` Pavel Machek
2003-05-08 19:27 ` Ben Collins
2003-05-08 20:06 ` Pavel Machek
2003-05-08 19:47 ` Ben Collins
2003-05-08 20:09 ` David S. Miller
2003-05-08 20:26 ` David Mosberger
2003-05-08 20:33 ` Arjan van de Ven
2003-05-08 21:11 ` David Mosberger
2003-05-08 15:23 ` Arnd Bergmann [this message]
2003-05-07 15:28 ` Pavel Machek
2003-05-07 16:04 ` David S. Miller
2003-05-07 19:13 ` Arnd Bergmann
2003-05-07 18:12 ` David S. Miller
2003-05-07 23:50 ` Arnd Bergmann
2003-05-08 10:35 ` David S. Miller
2003-05-07 22:20 ` Alan Cox
2003-05-08 20:33 ` Pavel Machek
2003-05-08 20:43 ` David S. Miller
2003-05-08 23:03 ` Pavel Machek
2003-05-08 23:35 ` Arnd Bergmann
2003-05-08 22:48 ` Arnd Bergmann
2003-05-08 23:22 ` Pavel Machek
2003-05-07 13:18 ` Arnd Bergmann
2003-05-07 14:01 ` Carl-Daniel Hailfinger
2003-05-07 15:16 ` Pavel Machek
2003-05-07 15:46 ` Arnd Bergmann
2003-05-07 16:07 ` Jens Axboe
2003-05-07 16:20 ` Arnd Bergmann
2003-05-07 10:27 Pavel Machek
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=200305081723.19285.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=davem@redhat.com \
--cc=hch@infradead.org \
--cc=kraxel@bytesex.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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