public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tao Ma <tao.ma@oracle.com>
To: Mike Christie <michaelc@cs.wisc.edu>
Cc: open-iscsi@googlegroups.com, linux-kernel@vger.kernel.org,
	"tao.ma" <tao.ma@oracle.com>
Subject: lockdep warning for iscsi in 2.6.33-rc6
Date: Tue, 09 Feb 2010 14:59:27 +0800	[thread overview]
Message-ID: <4B7107CF.3060703@oracle.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 104 bytes --]

Hi Mike,
	I meet with a lockdep warning for iscsi in 2.6.33-rc6.
the lockdep is attached.

Regards,
Tao

[-- Attachment #2: iscsi_lockdep --]
[-- Type: text/plain, Size: 8887 bytes --]

Feb  9 11:39:29 ocfs2-test7 kernel: =======================================================
Feb  9 11:39:29 ocfs2-test7 kernel: [ INFO: possible circular locking dependency detected ]
Feb  9 11:39:29 ocfs2-test7 kernel: 2.6.33-rc6 #6
Feb  9 11:39:29 ocfs2-test7 kernel: -------------------------------------------------------
Feb  9 11:39:29 ocfs2-test7 kernel: iscsid/2960 is trying to acquire lock:
Feb  9 11:39:29 ocfs2-test7 kernel:  (&shost->scan_mutex){+.+.+.}, at: [<ffffffffa006aec5>] scsi_scan_target+0x6d/0xad [scsi_mod]
Feb  9 11:39:29 ocfs2-test7 kernel: 
Feb  9 11:39:29 ocfs2-test7 kernel: but task is already holding lock:
Feb  9 11:39:30 ocfs2-test7 kernel:  (&ihost->mutex){+.+...}, at: [<ffffffffa02aeb34>] iscsi_user_scan_session+0x96/0x14b [scsi_transport_iscsi]
Feb  9 11:39:30 ocfs2-test7 kernel: 
Feb  9 11:39:30 ocfs2-test7 kernel: which lock already depends on the new lock.
Feb  9 11:39:30 ocfs2-test7 kernel: 
Feb  9 11:39:30 ocfs2-test7 kernel: 
Feb  9 11:39:30 ocfs2-test7 kernel: the existing dependency chain (in reverse order) is:
Feb  9 11:39:30 ocfs2-test7 kernel: 
Feb  9 11:39:30 ocfs2-test7 kernel: -> #2 (&ihost->mutex){+.+...}:
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffff820641ea>] validate_chain+0xa31/0xedb
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffff82064f9c>] __lock_acquire+0x908/0x95f
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffff82065d62>] lock_acquire+0xbc/0x102
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffff8232d3c5>] mutex_lock_nested+0x48/0x29f
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffffa02aeb34>] iscsi_user_scan_session+0x96/0x14b [scsi_transport_iscsi]
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffff8221702f>] device_for_each_child+0x32/0x64
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffffa02aea83>] iscsi_user_scan+0x28/0x2a [scsi_transport_iscsi]
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffffa006b979>] store_scan+0x9d/0xc9 [scsi_mod]
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffff82216c88>] dev_attr_store+0x1b/0x1d
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffff8212b78b>] sysfs_write_file+0xf7/0x133
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffff820d881e>] vfs_write+0xae/0x14a
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffff820d8d2a>] sys_write+0x47/0x6f
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffff8200296b>] system_call_fastpath+0x16/0x1b
Feb  9 11:39:30 ocfs2-test7 kernel: 
Feb  9 11:39:30 ocfs2-test7 kernel: -> #1 (s_active){++++.+}:
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffff820641ea>] validate_chain+0xa31/0xedb
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffff82064f9c>] __lock_acquire+0x908/0x95f
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffff82065d62>] lock_acquire+0xbc/0x102
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffff8212c885>] sysfs_addrm_finish+0xba/0x125
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffff8212adbe>] sysfs_hash_and_remove+0x4f/0x6b
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffff8212ce6f>] sysfs_remove_link+0x1c/0x1e
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffff8221a10e>] driver_sysfs_remove+0x29/0x3c
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffff8221a3e5>] driver_probe_device+0xdc/0x139
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffff8221a627>] __device_attach+0x33/0x3c
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffff822194a9>] bus_for_each_drv+0x4d/0x80
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffff8221a541>] device_attach+0x60/0x77
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffff82219445>] bus_probe_device+0x22/0x39
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffff82217edb>] device_add+0x44c/0x5d3
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffffa006c026>] scsi_sysfs_add_sdev+0xb8/0x1e2 [scsi_mod]
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffffa006a0e4>] scsi_probe_and_add_lun+0xadd/0xbcf [scsi_mod]
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffffa006adf7>] __scsi_add_device+0xb6/0xe5 [scsi_mod]
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffffa00b16d6>] ata_scsi_scan_host+0x89/0x17a [libata]
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffffa00afb25>] async_port_probe+0xa9/0xb4 [libata]
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffff8205a5cc>] async_thread+0x115/0x206
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffff82054a5d>] kthread+0x7d/0x85
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffff82003794>] kernel_thread_helper+0x4/0x10
Feb  9 11:39:30 ocfs2-test7 kernel: 
Feb  9 11:39:30 ocfs2-test7 kernel: -> #0 (&shost->scan_mutex){+.+.+.}:
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffff82063ed6>] validate_chain+0x71d/0xedb
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffff82064f9c>] __lock_acquire+0x908/0x95f
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffff82065d62>] lock_acquire+0xbc/0x102
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffff8232d3c5>] mutex_lock_nested+0x48/0x29f
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffffa006aec5>] scsi_scan_target+0x6d/0xad [scsi_mod]
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffffa02aeb9f>] iscsi_user_scan_session+0x101/0x14b [scsi_transport_iscsi]
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffff8221702f>] device_for_each_child+0x32/0x64
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffffa02aea83>] iscsi_user_scan+0x28/0x2a [scsi_transport_iscsi]
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffffa006b979>] store_scan+0x9d/0xc9 [scsi_mod]
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffff82216c88>] dev_attr_store+0x1b/0x1d
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffff8212b78b>] sysfs_write_file+0xf7/0x133
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffff820d881e>] vfs_write+0xae/0x14a
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffff820d8d2a>] sys_write+0x47/0x6f
Feb  9 11:39:30 ocfs2-test7 kernel:        [<ffffffff8200296b>] system_call_fastpath+0x16/0x1b
Feb  9 11:39:30 ocfs2-test7 kernel: 
Feb  9 11:39:30 ocfs2-test7 kernel: other info that might help us debug this:
Feb  9 11:39:31 ocfs2-test7 kernel: 
Feb  9 11:39:31 ocfs2-test7 kernel: 4 locks held by iscsid/2960:
Feb  9 11:39:31 ocfs2-test7 kernel:  #0:  (&buffer->mutex){+.+.+.}, at: [<ffffffff8212b6cd>] sysfs_write_file+0x39/0x133
Feb  9 11:39:31 ocfs2-test7 kernel:  #1:  (s_active){++++.+}, at: [<ffffffff8212cb61>] sysfs_get_active_two+0x1f/0x44
Feb  9 11:39:31 ocfs2-test7 kernel:  #2:  (s_active){++++.+}, at: [<ffffffff8212cb6e>] sysfs_get_active_two+0x2c/0x44
Feb  9 11:39:31 ocfs2-test7 kernel:  #3:  (&ihost->mutex){+.+...}, at: [<ffffffffa02aeb34>] iscsi_user_scan_session+0x96/0x14b [scsi_transport_iscsi]
Feb  9 11:39:31 ocfs2-test7 kernel: 
Feb  9 11:39:31 ocfs2-test7 kernel: stack backtrace:
Feb  9 11:39:31 ocfs2-test7 kernel: Pid: 2960, comm: iscsid Not tainted 2.6.33-rc6 #6
Feb  9 11:39:31 ocfs2-test7 kernel: Call Trace:
Feb  9 11:39:31 ocfs2-test7 kernel:  [<ffffffff820630b2>] print_circular_bug+0xb3/0xc1
Feb  9 11:39:31 ocfs2-test7 kernel:  [<ffffffff82063ed6>] validate_chain+0x71d/0xedb
Feb  9 11:39:31 ocfs2-test7 kernel:  [<ffffffff820613d0>] ? add_lock_to_list+0x82/0xc2
Feb  9 11:39:31 ocfs2-test7 kernel:  [<ffffffff82064f9c>] __lock_acquire+0x908/0x95f
Feb  9 11:39:31 ocfs2-test7 kernel:  [<ffffffff82065d62>] lock_acquire+0xbc/0x102
Feb  9 11:39:31 ocfs2-test7 kernel:  [<ffffffffa006aec5>] ? scsi_scan_target+0x6d/0xad [scsi_mod]
Feb  9 11:39:31 ocfs2-test7 kernel:  [<ffffffff8232d3c5>] mutex_lock_nested+0x48/0x29f
Feb  9 11:39:31 ocfs2-test7 kernel:  [<ffffffffa006aec5>] ? scsi_scan_target+0x6d/0xad [scsi_mod]
Feb  9 11:39:31 ocfs2-test7 kernel:  [<ffffffff820622ef>] ? mark_held_locks+0x49/0x69
Feb  9 11:39:31 ocfs2-test7 kernel:  [<ffffffff8232ef48>] ? _raw_spin_unlock_irqrestore+0x3f/0x47
Feb  9 11:39:31 ocfs2-test7 kernel:  [<ffffffffa006aec5>] scsi_scan_target+0x6d/0xad [scsi_mod]
Feb  9 11:39:31 ocfs2-test7 kernel:  [<ffffffffa02aeb9f>] iscsi_user_scan_session+0x101/0x14b [scsi_transport_iscsi]
Feb  9 11:39:31 ocfs2-test7 kernel:  [<ffffffffa02aea9e>] ? iscsi_user_scan_session+0x0/0x14b [scsi_transport_iscsi]
Feb  9 11:39:31 ocfs2-test7 kernel:  [<ffffffff8221702f>] device_for_each_child+0x32/0x64
Feb  9 11:39:31 ocfs2-test7 kernel:  [<ffffffffa02aea83>] iscsi_user_scan+0x28/0x2a [scsi_transport_iscsi]
Feb  9 11:39:31 ocfs2-test7 kernel:  [<ffffffffa006b979>] store_scan+0x9d/0xc9 [scsi_mod]
Feb  9 11:39:31 ocfs2-test7 kernel:  [<ffffffff8212cb6e>] ? sysfs_get_active_two+0x2c/0x44
Feb  9 11:39:31 ocfs2-test7 kernel:  [<ffffffff82216c88>] dev_attr_store+0x1b/0x1d
Feb  9 11:39:31 ocfs2-test7 kernel:  [<ffffffff8212b78b>] sysfs_write_file+0xf7/0x133
Feb  9 11:39:31 ocfs2-test7 kernel:  [<ffffffff820d881e>] vfs_write+0xae/0x14a
Feb  9 11:39:31 ocfs2-test7 kernel:  [<ffffffff820d8d2a>] sys_write+0x47/0x6f
Feb  9 11:39:31 ocfs2-test7 kernel:  [<ffffffff8200296b>] system_call_fastpath+0x16/0x1b

             reply	other threads:[~2010-02-09  7:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-09  6:59 Tao Ma [this message]
2010-02-09 19:30 ` lockdep warning for iscsi in 2.6.33-rc6 Mike Christie
2010-02-10  0:42   ` Tao Ma
2010-02-12 17:21     ` Mike Christie
2010-02-11 20:08 ` Maciej Rutecki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B7107CF.3060703@oracle.com \
    --to=tao.ma@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    --cc=open-iscsi@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox