Why not use kdev_t?
> This means that all relevant ioctl numbers will have to change.
> Maybe it would be nice for security if there were a guarantee
> about the amount of memory written by the kernel, so that it
> would be impossible to crash a well-written application on a
> more recent kernel. Perhaps something like
>
> linuxioctl( int ioctl, int *version, int *length, void *data );
The traditional approach would be to put this into the structure of
the plain old ioctl(2):
struct foo{
unsigned short size;
unsigned short version;
other data;
};
struct foo x;
x.size=sizeof(x);
x.version=1;
ioctl...
Regards,
Martin