All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: "Asutosh Das (asd)" <quic_asutoshd@quicinc.com>,
	"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>,
	linux-scsi@vger.kernel.org,
	Adrian Hunter <adrian.hunter@intel.com>,
	dh0421.hwang@samsung.com, Asutosh Das <asutoshd@codeaurora.org>,
	"James E.J. Bottomley" <jejb@linux.ibm.com>,
	Bean Huo <beanhuo@micron.com>, Avri Altman <avri.altman@wdc.com>,
	Jinyoung Choi <j-young.choi@samsung.com>
Subject: Re: [PATCH] scsi: ufs: Fix deadlocks between power management and error handler
Date: Mon, 19 Sep 2022 16:17:56 -0700	[thread overview]
Message-ID: <f75c75e2-b2eb-abc1-c600-86c6ee235fda@acm.org> (raw)
In-Reply-To: <2be5b57f-f367-2e28-c317-e0daedcfb3a4@quicinc.com>

On 9/18/22 20:10, Asutosh Das (asd) wrote:
> Say, there's a PWR_FATAL error in ufshcd_wl_suspend().
> Wouldn't there be a scenario in which the suspend and error handler may 
> run simultaneously?

This is something I need to look further into.

> Do you see issues when that happens? How about when shutdown runs 
> simultaneously with error handler?

Hmm ... I don't think that my patch changes the interaction between the 
shutdown handler and the error handler?

Thanks,

Bart.

  reply	other threads:[~2022-09-19 23:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-16 18:42 [PATCH] scsi: ufs: Fix deadlocks between power management and error handler Bart Van Assche
2022-09-19  3:10 ` Asutosh Das (asd)
2022-09-19 23:17   ` Bart Van Assche [this message]
2022-09-19 11:34 ` Adrian Hunter
2022-09-19 13:54   ` Bart Van Assche
2022-09-19 17:21     ` Adrian Hunter
2022-09-19 23:22       ` Bart Van Assche

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=f75c75e2-b2eb-abc1-c600-86c6ee235fda@acm.org \
    --to=bvanassche@acm.org \
    --cc=adrian.hunter@intel.com \
    --cc=asutoshd@codeaurora.org \
    --cc=avri.altman@wdc.com \
    --cc=beanhuo@micron.com \
    --cc=dh0421.hwang@samsung.com \
    --cc=j-young.choi@samsung.com \
    --cc=jaegeuk@kernel.org \
    --cc=jejb@linux.ibm.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=quic_asutoshd@quicinc.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.