Re: unlocked_ioctl explanation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



2011/5/19 Ezequiel García <elezegarcia@xxxxxxxxxxxx>
>
> Thanks Dave for your answer. I guess the same question has been answered several times before. For the interest reader, I've found these:
>
> http://unix.stackexchange.com/questions/4711/what-is-the-difference-between-ioctl-unlocked-ioctl-and-compat-ioctl
>
> http://lwn.net/Articles/119652/
>
> http://www.mail-archive.com/kernelnewbies@xxxxxxxxxxxx/msg00269.html
>
> I have a remaining question, though. In the lwn article I read this:
>
> "The ioctl() system call has long been out of favor among the kernel developers, who see it as a completely uncontrolled entry point into the kernel".
>
> Is this pointing that ioctl() is planning to get removed from the kernel ? In that case what's the currently preferred mechanism for giving 'control commands' to device drivers ?

I would bet for 'sysfs'.

thanks,
Daniel.

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies



[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux