LiS-2.18.0 : hang on close and i_unlink

Hi,
 
I'm curious if people saw hangs with the trace like this:
 
#0 [f5cb0c5c] schedule at c02cf361 
#1 [f5cb0cbc] __down_interruptible at c02cea62 
#2 [f5cb0cf4] __down_failed_interruptible at c02ceace 
#3 [f5cb0d00] .text.lock.KBUILD_BASENAME (via lis_down_fcn) at f956be61
#4 [f5cb0d20] lis_down_nosig_fcn at f956bcb3 
#5 [f5cb0d48] lis_await_qsched at f9544dcb 
#6 [f5cb0e1c] lis_qdetach at f954c33f 
#7 [f5cb0eac] lis_dismantle at f954d074 
#8 [f5cb0ec0] lis_doclose at f9554fb1 
#9 [f5cb0f68] lis_strclose at f955920a 
#10 [f5cb0f9c] __fput at c015a8fc 
#11 [f5cb0fb0] filp_close at c0159540 
#12 [f5cb0fc0] system_call at c02d10c8 
 
or like this:
 
#0 [f465dbd4] schedule at c02cf361 
#1 [f465dc34] __down_interruptible at c02cea62 
#2 [f465dc6c] __down_failed_interruptible at c02ceace 
#3 [f465dc78] .text.lock.KBUILD_BASENAME (via lis_down_fcn) at f956be61
#4 [f465dc98] lis_down_nosig_fcn at f956bcb3 
#5 [f465dcc0] lis_await_qsched at f9544dcb 
#6 [f465dd94] lis_i_unlink at f9556049 
#7 [f465de14] lis_strioctl at f9556fcb 
#8 [f465dfa8] sys_write at c0159eef 
#9 [f465dfc0] system_call at c02d10c8 
 
 
The piece of code in 2.16.18, which evolved into the lis_await_qsched()
function in 2.18.0,  used to have lis_spin_lock_irqsave(&lis_qhead_lock, &psw) calls.
 
The lis_await_qsched() from 2.18.0 do not do these lis_spin_lock_irqsave(&lis_qhead_lock, &psw)
calls anymore. I'm thinking that might be the problem resulting in the aforementioned hangs.
 
Any comments?
--
Eugene
 
 
 
___________________________________________________
Try the New Netscape Mail Today!
Virtually Spam-Free | More Storage | Import Your Contact List
http://mail.netscape.com