linux-kernel - Re: Ioctl

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20110131115152.b327044f.rdunlap@xenotime.net>
Date:	Mon, 31 Jan 2011 11:51:52 -0800
From:	Randy Dunlap <rdunlap@...otime.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 wrote:

> Hello,
> 
> 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.
> 
> There is tons of stuff in my code that I don't yet understand which requires
> the ioctl function.  What is the best way for me to either get the ioctl
> working in 2.6.37, or the quickest way to work around it???

ioctl() is still around.

fs/ioctl.c:
SYSCALL_DEFINE3(ioctl, unsigned int, fd, unsigned int, cmd, unsigned long, arg)
{

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
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/