| 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: <20110131125524.116fe96e@bike.lwn.net> Date: Mon, 31 Jan 2011 12:55:24 -0700 From: Jonathan Corbet <corbet@....net> To: "Brian D. McGrew" <brian@...ionpro.com> Cc: <linux-kernel@...r.kernel.org> Subject: Re: Ioctl On Mon, 31 Jan 2011 11:39:13 -0800 "Brian D. McGrew" <brian@...ionpro.com> wrote: > I'm very new at working with the kernel and device drivers and I'm trying to > bring ours drivers up from a 2.6.16 kernel to 2.6.37. I'm noticing that > ioctl() doesn't seem to be raound anymore, or at least I can't find it. What you almost certainly want is unlocked_ioctl(), which handles ioctl() calls but lacks the protection of the (soon to be removed) big kernel lock. If your driver is properly written, you should have no problem using unlocked_ioctl(), but do note that the function prototype is a little different. jon -- 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