| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <46312AEE.1000302@microgate.com> Date: Thu, 26 Apr 2007 16:42:54 -0600 From: Paul Fulghum <paulkf@...rogate.com> To: Arnd Bergmann <arnd@...db.de> CC: Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: compat_ioctl question Arnd Bergmann wrote: > It depends a lot on what your specific driver does in the ioctl > handler, but normally you should define a compat_ioctl() function. > What driver are you talking about? drivers/char/synclink.c drivers/char/synclinkmp.c drivers/char/synclink_gt.c drivers/char/pcmcia/synclink_cs.c All use the same set of ioctl() codes that are peculiar to the synclink drivers. Defining compat_ioctl() seems to be the best way, but that will require modifying the base tty code to allow the individual tty drivers to register compat_ioctl(). Currently the tty file ops do not include that and tty_io.c does not register a compat_ioctl(), instead relying on compat_ioctl.h and compat_ioctl.c -- Paul - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists