From a7a20d103994fd760766e6c9d494daa569cbfe06 Mon Sep 17 00:00:00 2001 From: Dan Williams Date: Thu, 22 Mar 2012 17:05:11 -0700 Subject: [SCSI] sd: limit the scope of the async probe domain sd injects and synchronizes probe work on the global kernel-wide domain. This runs into conflict with PM that wants to perform resume actions in async context: [ 494.237079] INFO: task kworker/u:3:554 blocked for more than 120 seconds. [ 494.294396] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 494.360809] kworker/u:3 D 0000000000000000 0 554 2 0x00000000 [ 494.420739] ffff88012e4d3af0 0000000000000046 ffff88013200c160 ffff88012e4d3fd8 [ 494.484392] ffff88012e4d3fd8 0000000000012500 ffff8801394ea0b0 ffff88013200c160 [ 494.548038] ffff88012e4d3ae0 00000000000001e3 ffffffff81a249e0 ffff8801321c5398 [ 494.611685] Call Trace: [ 494.632649] [] schedule+0x5a/0x5c [ 494.674687] [] async_synchronize_cookie_domain+0xb6/0x112 [ 494.734177] [] ? __init_waitqueue_head+0x50/0x50 [ 494.787134] [] ? scsi_remove_target+0x48/0x48 [ 494.837900] [] async_synchronize_cookie+0x15/0x17 [ 494.891567] [] async_synchronize_full+0x54/0x70 <-- here we wait for async contexts to complete [ 494.943783] [] ? async_synchronize_full_domain+0x1a/0x1a [ 495.002547] [] sd_remove+0x2c/0xa2 [sd_mod] [ 495.051861] [] __device_release_driver+0x86/0xcf [ 495.104807] [] device_release_driver+0x25/0x32 <-- here we take device_lock() [ 853.511341] INFO: task kworker/u:4:549 blocked for more than 120 seconds. [ 853.568693] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 853.635119] kworker/u:4 D ffff88013097b5d0 0 549 2 0x00000000 [ 853.695129] ffff880132773c40 0000000000000046 ffff880130790000 ffff880132773fd8 [ 853.758990] ffff880132773fd8 0000000000012500 ffff88013288a0b0 ffff880130790000 [ 853.822796] 0000000000000246 0000000000000040 ffff88013097b5c8 ffff880130790000 [ 853.886633] Call Trace: [ 853.907631] [] schedule+0x5a/0x5c [ 853.949670] [] __mutex_lock_common+0x220/0x351 [ 854.001225] [] ? device_resume+0x58/0x1c4 [ 854.049082] [] ? device_resume+0x58/0x1c4 [ 854.097011] [] mutex_lock_nested+0x2f/0x36 <-- here we wait for device_lock() [ 854.145591] [] device_resume+0x58/0x1c4 [ 854.192066] [] async_resume+0x1e/0x45 [ 854.237019] [] async_run_entry_fn+0xc6/0x173 <-- ...while running in async context Provide a 'scsi_sd_probe_domain' so that async probe actions actions can be flushed without regard for the state of PM, and allow for the resume path to handle devices that have transitioned from SDEV_QUIESCE to SDEV_DEL prior to resume. Acked-by: Alan Stern [alan: uplevel scsi_sd_probe_domain, clarify scsi_device_resume] Signed-off-by: Dan Williams [jejb: remove unneeded config guards in include file] Signed-off-by: James Bottomley --- drivers/scsi/scsi_pm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'drivers/scsi/scsi_pm.c') diff --git a/drivers/scsi/scsi_pm.c b/drivers/scsi/scsi_pm.c index c4670642d023..f661a41fa4c6 100644 --- a/drivers/scsi/scsi_pm.c +++ b/drivers/scsi/scsi_pm.c @@ -97,7 +97,7 @@ static int scsi_bus_prepare(struct device *dev) { if (scsi_is_sdev_device(dev)) { /* sd probing uses async_schedule. Wait until it finishes. */ - async_synchronize_full(); + async_synchronize_full_domain(&scsi_sd_probe_domain); } else if (scsi_is_host_device(dev)) { /* Wait until async scanning is finished */ -- cgit v1.2.3-59-g8ed1b