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: <p73bqha3b33.fsf@bingen.suse.de> Date: 27 Apr 2007 02:38:56 +0200 From: Andi Kleen <andi@...stfloor.org> To: Paul Fulghum <paulkf@...rogate.com> Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: compat_ioctl question Paul Fulghum <paulkf@...rogate.com> writes: > > 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. (1) is really the recommended solution for all new code I would recommend you modify the tty driver to pass compat_ioctl through through. Should not do very hard. -Andi - 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/