All of lore.kernel.org
 help / color / mirror / Atom feed
From: Can Guo <cang@codeaurora.org>
To: asutoshd@codeaurora.org, nguyenb@codeaurora.org,
	hongwus@codeaurora.org, "Bean Huo (beanhuo)" <beanhuo@micron.com>,
	rnayak@codeaurora.org, linux-scsi@vger.kernel.org,
	kernel-team@android.com, saravanak@google.com,
	salyzyn@google.com, cang@codeaurora.org
Subject: Re: [PATCH v2 0/2] Fix some racing problems btw err_handler and paths like system PM ops and the task abort callback
Date: Tue, 20 Oct 2020 10:33:13 +0800	[thread overview]
Message-ID: <e45273aa4cab164a9f8ec2c2dd1c208e@codeaurora.org> (raw)
In-Reply-To: <1600757252-23048-1-git-send-email-cang@codeaurora.org>

Hi Bean,

On 2020-09-22 14:47, Can Guo wrote:
> 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 v1:
> - Removed Change-Id from commit msg
> 
> Can Guo (2):
>   scsi: ufs: Serialize eh_work with system PM events and async scan
>   scsi: ufs: Fix a racing problem between ufshcd_abort and eh_work
> 
>  drivers/scsi/ufs/ufshcd.c | 122 
> ++++++++++++++++++++++++++++++++--------------
>  drivers/scsi/ufs/ufshcd.h |   3 ++
>  2 files changed, 89 insertions(+), 36 deletions(-)

How is your test of the 2 patches going? Could you please give your
review since they've been here for a while.

Thanks,

Can Guo.

      parent reply	other threads:[~2020-10-20  2:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-22  6:47 [PATCH v2 0/2] Fix some racing problems btw err_handler and paths like system PM ops and the task abort callback Can Guo
2020-09-22  6:47 ` [PATCH v1 1/2] scsi: ufs: Serialize eh_work with system PM events and async scan Can Guo
2020-09-22  6:47 ` [PATCH v1 2/2] scsi: ufs: Fix a racing problem between ufshcd_abort and eh_work Can Guo
2020-10-20  2:33 ` Can Guo [this message]

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=e45273aa4cab164a9f8ec2c2dd1c208e@codeaurora.org \
    --to=cang@codeaurora.org \
    --cc=asutoshd@codeaurora.org \
    --cc=beanhuo@micron.com \
    --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 \
    /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.