内核新的ioctl方式---- unlocked_ioctl和compat_ioctl
来源:互联网 发布:java基础 学javascript 编辑:程序博客网 时间:2024/05/16 01:52
http://lwn.net/Articles/119652/
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. Given the vast number of applications which expect ioctl() to be present, however, it will not go away anytime soon. So it is worth the trouble to ensure that ioctl()calls are performed quickly and correctly - and that they do not unnecessarily impact the rest of the system.
ioctl() is one of the remaining parts of the kernel which runs under the Big Kernel Lock (BKL). In the past, the usage of the BKL has made it possible for long-running ioctl() methods to create long latencies for unrelated processes. Recent changes, which have made BKL-covered code preemptible, have mitigated that problem somewhat. Even so, the desire to eventually get rid of the BKL altogether suggests that ioctl() should move out from under its protection.
Simply removing the lock_kernel() call before calling ioctl() methods is not an option, however. Each one of those methods must first be audited to see what other locking may be necessary for it to run safely outside of the BKL. That is a huge job, one which would be hard to do in a single "flag day" operation. So a migration path must be provided. As of 2.6.11, that path will exist.
The patch (by Michael s. Tsirkin) adds a new member to the file_operations structure:
long (*unlocked_ioctl) (struct file *filp, unsigned int cmd, unsigned long arg);
If a driver or filesystem provides an unlocked_ioctl() method, it will be called in preference to the older ioctl(). The differences are that the inode argument is not provided (it's available as filp->f_dentry->d_inode) and the BKL is not taken prior to the call. All new code should be written with its own locking, and should use unlocked_ioctl(). Old code should be converted as time allows. For code which must run on multiple kernels, there is a new HAVE_UNLOCKED_IOCTLmacro which can be tested to see if the newer method is available or not.
Michael's patch adds one other operation:
long (*compat_ioctl) (struct file *filp, unsigned int cmd, unsigned long arg);
If this method exists, it will be called (without the BKL) whenever a 32-bit process calls ioctl() on a 64-bit system. It should then do whatever is required to convert the argument to native data types and carry out the request. If compat_ioctl() is not provided, the older conversion mechanism will be used, as before. The HAVE_COMPAT_IOCTL macro can be tested to see if this mechanism is available on any given kernel.
The compat_ioctl() method will probably filter down into a few subsystems. Andi Kleen has posted patches adding new compat_ioctl() methods to theblock_device_operations and scsi_host_template structures, for example, though those patches have not been merged as of this writing.
- 内核新的ioctl方式---- unlocked_ioctl和compat_ioctl
- 内核新的ioctl方式---- unlocked_ioctl和compat_ioctl
- 内核新的ioctl方式---- unlocked_ioctl和compat_ioctl
- 内核新的ioctl方式--unlocked_ioctl和compat_ioctl(解决error:unknown field 'ioctl' specified in initializer)
- 关于ioctl,unlocked_ioctl和compat_ioctl执行的顺序
- ioctl/unlocked_ioctl/compat_ioctl
- unlocked_ioctl和compat_ioctl
- unlocked_ioctl和compat_ioctl
- unlocked_ioctl和compat_ioctl
- unlocked_ioctl和compat_ioctl
- new way of ioctl --- unlocked_ioctl & compat_ioctl
- ioctl与unlocked_ioctl的区别
- unlocked_ioctl取代ioctl,内核以及应用
- struct file_operations中 ioctl 和 unlocked_ioctl
- ioctl 与unlocked_ioctl之间的转换
- ioctl compat_ioctl unlock_ioctl
- ioctl compat_ioctl与unlock_ioctl
- ioctl 变成了 unlocked_ioctl
- iOS TableView滚动到最底部
- NestedScrolling 嵌套滑动机制:原理简单分析(二)
- C#预处理器指令
- U盘不能卸载,直接拔掉再插入提示:“目录损坏
- body{display:none}
- 内核新的ioctl方式---- unlocked_ioctl和compat_ioctl
- Android开发---加载h5界面
- 如何对java多源文件编译
- PowerManagerService深入分析
- mysql替换字段中部分字符串
- 代码段、数据段、堆、栈
- 嵌入式 uboot命令及内核启动参数
- C++——字典树(Trie树)模板——统计难题(HDU1251)
- Fiddler监听报错