Skip to content
  1. Oct 18, 2018
    • Bryant G. Ly's avatar
      scsi: ibmvscsi_tgt: Remove target_wait_for_sess_cmd() · a1ad38a6
      Bryant G. Ly authored
      
      
      There is currently a bug with the driver where there is never a call to
      target_sess_cmd_list_set_waiting(), it only called
      target_wait_for_sess_cmd(), which basically means that the sess_wait_list
      would always be empty.
      
      Thus, list_empty(&sess->sess_wait_list) = true,
      (eg: no se_cmd I/O is quiesced, because no se_cmd in sess_wait_list),
      since commit 712db3eb ("scsi: ibmvscsis: Properly deregister
      target sessions") in 4.9.y code.
      
      ibmvscsi_tgt does not remove the I_T Nexus when a VM is active so we can
      fix this issue by removing the call to target_wait_for_sess_cmd()
      altogether.
      
      Signed-off-by: default avatarBryant G. Ly <bly@catalogicsoftware.com>
      Reviewed-by: default avatarMike Christie <mchristi@redhat.com>
      Signed-off-by: default avatarMartin K. Petersen <martin.petersen@oracle.com>
      a1ad38a6
    • Evan Green's avatar
      scsi: ufs: Schedule clk gating work on correct queue · f4bb7704
      Evan Green authored
      
      
      With commit 10e5e375 ("scsi: ufs: Add clock ungating to a separate
      workqueue"), clock gating work was moved to a separate work queue with
      WQ_MEM_RECLAIM set, since clock gating could occur from a memory reclaim
      context. Unfortunately, clk_gating.gate_work was left queued via
      schedule_delayed_work, which is a system workqueue that does not have
      WQ_MEM_RECLAIM set.  Because ufshcd_ungate_work attempts to cancel
      gate_work, the following warning appears:
      
      [   14.174170] workqueue: WQ_MEM_RECLAIM ufs_clk_gating_0:ufshcd_ungate_work is flushing !WQ_MEM_RECLAIM events:ufshcd_gate_work
      [   14.174179] WARNING: CPU: 4 PID: 173 at kernel/workqueue.c:2440 check_flush_dependency+0x110/0x118
      [   14.205725] CPU: 4 PID: 173 Comm: kworker/u16:3 Not tainted 4.14.68 #1
      [   14.212437] Hardware name: Google Cheza (rev1) (DT)
      [   14.217459] Workqueue: ufs_clk_gating_0 ufshcd_ungate_work
      [   14.223107] task: ffffffc0f6a40080 task.stack: ffffff800a490000
      [   14.229195] PC is at check_flush_dependency+0x110/0x118
      [   14.234569] LR is at check_flush_dependency+0x110/0x118
      [   14.239944] pc : [<ffffff80080cad14>] lr : [<ffffff80080cad14>] pstate: 60c001c9
      [   14.333050] Call trace:
      [   14.427767] [<ffffff80080cad14>] check_flush_dependency+0x110/0x118
      [   14.434219] [<ffffff80080cafec>] start_flush_work+0xac/0x1fc
      [   14.440046] [<ffffff80080caeec>] flush_work+0x40/0x94
      [   14.445246] [<ffffff80080cb288>] __cancel_work_timer+0x11c/0x1b8
      [   14.451433] [<ffffff80080cb4b8>] cancel_delayed_work_sync+0x20/0x30
      [   14.457886] [<ffffff80085b9294>] ufshcd_ungate_work+0x24/0xd0
      [   14.463800] [<ffffff80080cfb04>] process_one_work+0x32c/0x690
      [   14.469713] [<ffffff80080d0154>] worker_thread+0x218/0x338
      [   14.475361] [<ffffff80080d527c>] kthread+0x120/0x130
      [   14.480470] [<ffffff8008084814>] ret_from_fork+0x10/0x18
      
      The simple solution is to put the gate_work on the same WQ_MEM_RECLAIM
      work queue as the ungate_work.
      
      Fixes: 10e5e375 ("scsi: ufs: Add clock ungating to a separate workqueue")
      Signed-off-by: default avatarEvan Green <evgreen@chromium.org>
      Reviewed-by: default avatarDouglas Anderson <dianders@chromium.org>
      Reviewed-by: default avatarStephen Boyd <swboyd@chromium.org>
      Signed-off-by: default avatarMartin K. Petersen <martin.petersen@oracle.com>
      f4bb7704
  2. Oct 17, 2018
  3. Oct 16, 2018