> There is a lis_lockq/lis_unlockq pair around the q_qinfo->qi_putp call > (see lis_safe_putmsg).
Is it OK to call lis_safe_putmsg() from interrupt context? If - yes, then a lis_lockqf/lis_unlockqf pair around the q_qinfo->qi_putp call in the lis_safe_putmsg() is not good enough since it does not disable interrupts. I.e. lis_lockqf is defined as lis_spin_lock_fcn(), whereas if lis_safe_putmsg() can be called from both thread and interrupt conrext the lock call should be .._irqsave. Otherwise deadlock is possible between thread and interrupt execution pathes. > There is also a a lis_lockq/lis_unlockq pair around > the q->q_qinfo->qi_srvp call in queuerun. The same as in above seems to be possible if queruuerun is executed in interrupt context. -- Eugene __________________________________________________________________ Introducing the New Netscape Internet Service. Only $9.95 a month -- Sign up today at http://isp.netscape.com/register Netscape. Just the Net You Need. New! Netscape Toolbar for Internet Explorer Search from anywhere on the Web and block those annoying pop-ups. Download now at http://channels.netscape.com/ns/search/install.jsp _______________________________________________ Linux-streams mailing list [EMAIL PROTECTED] http://gsyc.escet.urjc.es/mailman/listinfo/linux-streams
