Unserializing ioctl() system calls
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 5 lines · Kristofer
I noticed that even in the 2.6.6 code, callers to ioctl system call (
sys_ioctlinfs/ioctl.c) are serialized with {lock,unlock}_kernel().I realize that many kernel modules, and POSIX for that matter, may not be ready to make this more concurrent.
POSIX doesn't care how the kernel implements locking.
Quoted 3 lines
I propose adding a flag to indicate that the underlying module would like to support its own concurrency management, and thus we avoid grabbing the BKL around the
f_op->ioctlcall.
Better would be probably a unlocked_ioctl() entry point in f_op. Should be pretty easy to implement.
There is also the additional issue that on 64bit systems with 32bit userland the ioctl emulation currently relies on the BKL.
-Andi