Hi, On Friday 11 May 2007 23:18, Yin,Fengwei wrote: > > So if the evdev_release() is preempted at the point marked by another > process which will open the evdev, which will make operation sequence > like: > > --evdev->open in evdev_release() > -----> preempted > evdev->open++ and input_open_devie() > <----- reschedule > input_close_device() > > Should we introduce a mutex here? Or do I miss something? Thanks. >
Locking is completely absent in evdev. There was a patch introducing locking in recent -mm's but it got dropped. I need to refresh it. -- Dmitry - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
