Dave,
If you still nest on *current*, the problem will not go away.
For a kernel thread LiS it wills till break on a timeout
(TIMER_BH) executing on the same processor trying to acquire
the same lock as the kernel thread. For a BH LiS, you would
have to wrap the LiS BH with start_bh_atomic() and
end_bh_atomic() to lock out the TIMER_BH (bad idea).
On Fri, 16 Mar 2001, Dave Grothe wrote:
>
> Vassili:
>
> A couple of things come to mind:
> 1. This is a small point, but sometimes these bugs are stupid -- Are
> you using lis_spin_lock_irqsave and not just lis_spin_lock? The
> timer code is interrupt level and you need the "irqsave" to
> protect against it.
> 2. Given that the above stupid bug is not happening, would you try
> this again with LiS-2.12 when it comes out in a week or two?
> There has been some work done on locking.
>
> It is possible that LiS-2.11 does not protect itself well from timer
> interrupt processing. That has been improved in LiS-2.12.
>
> -- Dave
>
--
Brian F. G. Bidulock ¦ The reasonable man adapts himself to the ¦
[EMAIL PROTECTED] ¦ world; the unreasonable one persists in ¦
http://www.openss7.org/ ¦ trying to adapt the world to himself. ¦
¦ Therefore all progress depends on the ¦
¦ unreasonable man. -- George Bernard Shaw ¦
_______________________________________________
Linux-streams mailing list
[EMAIL PROTECTED]
http://gsyc.escet.urjc.es/mailman/listinfo/linux-streams
