> I've seen this question several times in this thread. I haven't seen the
> obvious answer, though.
> Have a new system call:
> ctlfd = open_device_control_fd(fd);
> If fd is something that doesn't have a control interface (say, it already
> is a control filehandle), this returns an appropriate error code.
It may have several. Which one?
FWIW, I think that mixing network and device ioctls is a bad idea. These
groups are very different and we'd be better off dealing with changes in
For devices... I'd say that fpath(2) (same type as getcwd(2)) would be
a good way to deal with that. Or fpath(3) - implemented via readlink(2)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/