Subject: Re: why is my ioctl not being called?
To: Bill Studenmund <wrstuden@nas.nasa.gov>
From: Brett Lymn <blymn@baea.com.au>
List: tech-kern
Date: 06/09/1999 10:25:35
According to Bill Studenmund:
>
>FIONBIO, FIOASYNC, FIOSETOWN, and FIOGETOWN. For a FIFO, block, or char
>device, everything else should go to a VOP_IOCTL on the vnode (see
>vn_ioctl() in vfs_vnops.c). Socket stuff of course goes elsewhere. :-)
>

Interesting.  In my case I am just making a pseudo-device to feed some
data into kernel space - something akin to the method that ipfilter
uses for loading it's rules.

Thanks to everyone's help I saw the bleeding obvious that I had
stuffed up the ioctl call by trying to pass a structure not the
pointer to it.  I fixed that and my ioctl now gets called and promptly
panics the kernel.  Which, while not what I wanted it is what I fully
expected to happen :-)  The bug hunt begins....

-- 
===============================================================================
Brett Lymn, Computer Systems Administrator, British Aerospace Australia
===============================================================================