b1124cd3ec
When an lldd invokes ->notify_port_event() it can trigger a chain of libsas events to: 1/ form the port and find the direct attached device 2/ if the attached device is an expander perform domain discovery A call to flush_workqueue() will only flush the initial port formation work. Currently libsas users need to call scsi_flush_work() up to the max depth of chain (which will grow from 2 to 3 when ata discovery is moved to its own discovery event). Instead of open coding multiple calls switch to use drain_workqueue() to flush sas work. drain_workqueue() does not handle new work submitted during the drain so libsas needs a bit of infrastructure to hold off unchained work submissions while a drain is in flight. A lldd ->notify() event is considered 'unchained' while a sas_discover_event() is 'chained'. As Tejun notes: "For now, I think it would be best to add private wrapper in libsas to support deferring unchained work items while draining." Signed-off-by: Dan Williams <dan.j.williams@intel.com> Signed-off-by: James Bottomley <JBottomley@Parallels.com> |
||
|---|---|---|
| .. | ||
| aic94xx_dev.c | ||
| aic94xx_dump.c | ||
| aic94xx_dump.h | ||
| aic94xx_hwi.c | ||
| aic94xx_hwi.h | ||
| aic94xx_init.c | ||
| aic94xx_reg_def.h | ||
| aic94xx_reg.c | ||
| aic94xx_reg.h | ||
| aic94xx_sas.h | ||
| aic94xx_scb.c | ||
| aic94xx_sds.c | ||
| aic94xx_sds.h | ||
| aic94xx_seq.c | ||
| aic94xx_seq.h | ||
| aic94xx_task.c | ||
| aic94xx_tmf.c | ||
| aic94xx.h | ||
| Kconfig | ||
| Makefile | ||