> >I mean race condition of vpeirq() using sw_demux while other > >process updates the list... aiieee? > > Do you see an obvious lock that's not hold while processing a list?
No, but lock is problem in itself. If ioctl locks the sw_demux, wanting to update something, during that very moment, vpeirq wants to use sw_demux it will find it locked and would be forced to sleep but as tasklets can't sleep that would lead to oops schedule() in interrupt i guess. Maybe I'm too cautious, or don't know the completeness of the source that's something Ralph was talking about regarding stability issues. Emard -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
