From: Paul Fulghum <paulkf@microgate.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: compat_ioctl question
Date: Thu, 26 Apr 2007 15:51:57 -0500 [thread overview]
Message-ID: <1177620717.5060.11.camel@amdx2.microgate.com> (raw)
I need to add ioctl translations for my driver to
allow 32 bit access on 64 bit systems.
After digging through the kernel code there seems to be
3 methods of doing this:
1. define compat_ioctl() file operation for device and
implement translation code in individual driver
2. add COMPATIBLE_IOCTL entry to include/linux/compat_ioctl.h
to mark an ioctl code as the same in any environment
3. add HANDLE_IOCTL entry to fs/compat_ioctl.c with translation code
implemented in the same file
There is no way to implement #1 for a tty driver without
modifying the kernel tty code to allow registration of a
compat_ioctl() handler.
#3 would put a lot of driver specific stuff in a common
kernel file. This method also seems to break if there
is an ioctl code collision.
All of these methods involve changes to code outside of my driver.
--
Before I spend a lot of time on this I need to know what the
officially sanctioned method is. I haven't found any definitive
documentation and a review of mailing list archives does not
suggest a prevailing opinion.
Does anyone have pointers on which way would be most likely
to be accepted as a patch?
Thanks,
Paul
--
Paul Fulghum
Microgate Systems, Ltd
next reply other threads:[~2007-04-26 20:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 20:51 Paul Fulghum [this message]
2007-04-26 21:37 ` compat_ioctl question Arnd Bergmann
2007-04-26 22:42 ` Paul Fulghum
2007-04-26 22:08 ` Arnd Bergmann
2007-04-26 23:15 ` Paul Fulghum
2007-05-02 17:52 ` [PATCH] tty add compat_ioctl method Paul Fulghum
2007-05-02 21:55 ` Arnd Bergmann
2007-05-02 23:03 ` Paul Fulghum
2007-05-02 22:28 ` Arnd Bergmann
2007-04-27 0:38 ` compat_ioctl question Andi Kleen
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=1177620717.5060.11.camel@amdx2.microgate.com \
--to=paulkf@microgate.com \
--cc=linux-kernel@vger.kernel.org \
/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