On Mon, May 19, 2008 at 8:21 PM, Jonathan Corbet wrote:
quoted text
> Mike Frysinger wrote:
>> this open func already has a spinlock protecting it.  doesnt that mean
>> we dont need the bkl in it ?
>
> The existence of a spinlock is a good sign.  But, until somebody has
> looked at the code and verified that said lock is really protecting
> everything, it's best to leave the BKL protection (which has always been
> there, just at a higher level) in place.

if the spinlock doesnt do what it's advertising (preventing mutual
access), then the BKL is needed.  if there's some UP behavior i'm not
aware of, then the BKL is needed.  otherwise, the BKL is not needed in
this driver.

i should prob rewrite this driver anyways ... the open code could
easily be replaced with some atomic funcs.
-mike
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/