From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Can Guo <cang@codeaurora.org>
Cc: asutoshd@codeaurora.org, nguyenb@codeaurora.org,
hongwus@codeaurora.org, rnayak@codeaurora.org,
linux-scsi@vger.kernel.org, kernel-team@android.com,
saravanak@google.com, salyzyn@google.com,
Stanley Chu <stanley.chu@mediatek.com>
Subject: Re: [PATCH V7 0/3] Minor fixes to UFS error handling
Date: Mon, 07 Dec 2020 18:31:57 -0500 [thread overview]
Message-ID: <yq1mtyp19en.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <1606910644-21185-1-git-send-email-cang@codeaurora.org> (Can Guo's message of "Wed, 2 Dec 2020 04:04:00 -0800")
Can,
> This series mainly fixes below two things which come along with UFS error
> handling in some corner cases.
> [1] Concurrency problems btw err_handler and paths like system suspend/resume/shutdown and async scan.
> [2] Race condition btw UFS error recovery and task abort which happens to W-LU during suspend/resume/shutdown.
Applied to 5.11/scsi-staging, thanks!
Stanley: Please verify conflict resolution with your event notification
series.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2020-12-07 23:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 12:04 [PATCH V7 0/3] Minor fixes to UFS error handling Can Guo
2020-12-02 12:04 ` [PATCH V7 1/3] scsi: ufs: Serialize eh_work with system PM events and async scan Can Guo
2020-12-02 12:04 ` Can Guo
2020-12-02 12:04 ` Can Guo
2020-12-02 12:04 ` [PATCH V7 2/3] scsi: ufs: Fix a race condition between ufshcd_abort and eh_work Can Guo
2020-12-03 2:21 ` Stanley Chu
2020-12-03 4:01 ` Can Guo
2020-12-03 4:51 ` Stanley Chu
2020-12-03 5:11 ` Can Guo
2020-12-03 5:19 ` Stanley Chu
2020-12-03 5:21 ` Can Guo
2020-12-02 12:04 ` [PATCH V7 3/3] scsi: ufs: Print host regs in IRQ handler when AH8 error happens Can Guo
2020-12-02 12:04 ` Can Guo
2020-12-02 12:04 ` Can Guo
2020-12-07 23:31 ` Martin K. Petersen [this message]
2020-12-08 5:04 ` [PATCH V7 0/3] Minor fixes to UFS error handling Stanley Chu
2020-12-09 17:23 ` Martin K. Petersen
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=yq1mtyp19en.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=asutoshd@codeaurora.org \
--cc=cang@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=stanley.chu@mediatek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.