[openib-general] Re: spinlock wrong CPU on CPU#1, ib_addr

[Or Gerlitz]

Sean Hefty wrote:

> it looks like the adaptor_list_lock in iser_adaptor_find_device() was 
> acquired while running on CPU 0, but an attempt was made to release it on CPU 1. 

Indeed.

The thing did not reproduce, moreover i can't see why a thread which was 
interrupted on one CPU resume its running on another CPU. For now, I 
will not change this code to lock irq's.

Or.