Re: Possible bug in keyboard.c (2.6.10)

[Pavel Machek]

Hi!

> > In short - raw mode in 2.6 is badly broken.
> 
> I think not just that. The whole keyboard input layer needs some serious 
> review. Just the complete lack of any locking is frightening, I'd really 
> like to know how the input layer could become the standard. I tried to 
> find a few times to find any discussion about the input layer design, but 
> I couldn't find anything.

Actually, at one point we went over inputs with vojtech and tried to
fix the locking. We tried adding spinlocks, but it got really ugly
really quickly. Then we figured out that set_bit() and friends should
be enough to do spinlock-equivalent without getting that ugly.

We did not have enough energy to solve plug/unplug races at that
point; but other races should have been fixed. It is possible that we
overlooked something and doing set_bit() instead of spinlocks is
broken. If it is so, please tell us. 

								Pavel
-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/