Re: Is this a preempt issue in drivers/input/evdev.c

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/

---

• Follow-Ups:
  • Re: Is this a preempt issue in drivers/input/evdev.c
    • From: Jens Axboe <[email protected]>

• References:
  • Is this a preempt issue in drivers/input/evdev.c
    • From: "Yin,Fengwei" <[email protected]>

• Prev by Date: Re: [PATCH] mm: swap prefetch improvements
• Next by Date: Re: 2.6.21-mm2: HDAPS? BUG: at kernel/mutex.c:311
• Previous by thread: Is this a preempt issue in drivers/input/evdev.c
• Next by thread: Re: Is this a preempt issue in drivers/input/evdev.c
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]