lkml.org 
[lkml]   [2010]   [Feb]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: lockdep warning for iscsi in 2.6.33-rc6
On 02/09/2010 12:59 AM, Tao Ma wrote:
> Hi Mike,
> I meet with a lockdep warning for iscsi in 2.6.33-rc6.
> the lockdep is attached.
>

If the lockdep output is saying that there is a problem with the iscsi
host taking its mutex then the scsi host mutex, I think that might be a
mistake in the lockdep detection. We always take the iscsi host mutex
then take the scsi host mutex.

Could it get confused if we are scanning two hosts at the same time? If
it is just looking at if a lock is being taken then it would look like
host1 has its ihost->mutex and then took its shost->mutex, but then
host2 could start to get scanned at the same time, and it is going to
take its ihost->mutex. It would then look like we are trying to grab a
ihost->mutex while holding a shost->mutex. However, the mutexs are not
global and they are different instances of the mutex because each host
has its own.

If that is not the problem, maybe it has something to do with some sysfs
lock and ata doing scanning while iscsi is.


\
 
 \ /
  Last update: 2010-02-09 20:33    [W:0.926 / U:0.428 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site