From: Can Guo <cang@codeaurora.org>
To: asutoshd@codeaurora.org, nguyenb@codeaurora.org,
hongwus@codeaurora.org, ziqichen@codeaurora.org,
rnayak@codeaurora.org, linux-scsi@vger.kernel.org,
kernel-team@android.com, saravanak@google.com,
salyzyn@google.com, cang@codeaurora.org
Subject: [PATCH v3 0/3] Fix some racing problems btw err_handler and paths like system PM ops and the task abort callback
Date: Mon, 16 Nov 2020 23:04:16 -0800 [thread overview]
Message-ID: <1605596660-2987-1-git-send-email-cang@codeaurora.org> (raw)
This series mainly fixes racing problems btw err_handler and paths like
system PM ops, async scan and task abort callback.
This series has been tested with error/fault injections to system PM
operations, async scan and task abort to the UFS device W-LU.
Change since v2:
- Added one more minor change into this series.
Change since v1:
- Removed Change-Id from commit msg
Can Guo (3):
scsi: ufs: Serialize eh_work with system PM events and async scan
scsi: ufs: Fix a racing problem between ufshcd_abort and eh_work
scsi: ufs: Print host regs in IRQ handler when AH8 error happens
drivers/scsi/ufs/ufshcd.c | 122 ++++++++++++++++++++++++++++++++--------------
drivers/scsi/ufs/ufshcd.h | 3 ++
2 files changed, 88 insertions(+), 37 deletions(-)
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project.
next reply other threads:[~2020-11-17 7:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 7:04 Can Guo [this message]
2020-11-17 7:04 ` [PATCH v3 1/3] scsi: ufs: Serialize eh_work with system PM events and async scan Can Guo
2020-11-25 2:48 ` hongwus
2020-12-01 2:41 ` Asutosh Das (asd)
2020-11-17 7:04 ` [PATCH v3 2/3] scsi: ufs: Fix a racing problem between ufshcd_abort and eh_work Can Guo
2020-12-01 2:42 ` Asutosh Das (asd)
2020-11-17 7:04 ` [PATCH v3 3/3] scsi: ufs: Print host regs in IRQ handler when AH8 error happens Can Guo
2020-11-17 17:23 ` Asutosh Das (asd)
2020-11-25 2:51 ` hongwus
2020-11-25 4:17 ` nguyenb
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=1605596660-2987-1-git-send-email-cang@codeaurora.org \
--to=cang@codeaurora.org \
--cc=asutoshd@codeaurora.org \
--cc=hongwus@codeaurora.org \
--cc=kernel-team@android.com \
--cc=linux-scsi@vger.kernel.org \
--cc=nguyenb@codeaurora.org \
--cc=rnayak@codeaurora.org \
--cc=salyzyn@google.com \
--cc=saravanak@google.com \
--cc=ziqichen@codeaurora.org \
/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