Re: [RFC] rfkill - Add support for input key to control wireless radio

On Sunday 03 December 2006 20:20, Arjan van de Ven wrote:
> this open_count thing smells fishy to me; what are the locking rules for
> it? What guarantees that the readers of it don't get the value changed
> underneath them between looking at the value and doing whatever action
> depends on it's value ?

Good point, a race condition could indeed occur in the only reader
that sends the signal to the userspace through the input device.
I'll fix this immediately.

Thanks,

Ivo
-
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/

---

• References:
  • [RFC] rfkill - Add support for input key to control wireless radio
    • From: Ivo van Doorn <[email protected]>
  • Re: [RFC] rfkill - Add support for input key to control wireless radio
    • From: Arjan van de Ven <[email protected]>

• Prev by Date: Re: [RFC] rfkill - Add support for input key to control wireless radio
• Next by Date: Re: [PATCH] Kbuild: add 3 more header files to get properly "unifdef"ed
• Previous by thread: Re: [RFC] rfkill - Add support for input key to control wireless radio
• Next by thread: Re: [RFC] rfkill - Add support for input key to control wireless radio
• 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]