|
Hi My daemon gets “Inappropriate ioctl” (ENOTTY)
from kernel ioctl handler (sys_ioctl() ->file_ioctl () ). This daemon is forked/exceed by the process which did
open() to the device file. The same logic works great in a normal booted system. Expecting
it to work during initrd stage. I have loaded the modules through /linuxrc. Can anyone tell me why a forked/excec child doing
sys_ioctl can encounter NULL ioctl handler during initrd stage. Though the
driver is loaded and parent process did open(/dev/XYZ, O_RDW) on the device
file. The kernel is 2.6.9. It works during initrd stages for
2.6.10 kernel and also worked for 2.4 kernels in past. The ioctl cmd passed
is =0x477cbc00. Is there a resource constraint. I am not very sure whats
happening. Any ideas will be helpful. Regards -vikas aggarwal |
