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
Subject: Re: [PATCH v5 0/2] Synchronize user layer access with system PM ops and error handling
Date: Thu, 14 Jan 2021 22:17:25 -0500 [thread overview]
Message-ID: <yq1czy6sxd4.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <1610594010-7254-1-git-send-email-cang@codeaurora.org> (Can Guo's message of "Wed, 13 Jan 2021 19:13:26 -0800")
Can,
> The 1st change is just a minor fix.
> The 2nd change is to synchronize user layer access through UFS sysfs
> nodes, so that system PM ops (suspend, resume and shutdown), error
> handling and async probe won't be disturbed by user layer access. The
> protection is only added to some sysfs nodes, not all of them.
Applied to 5.12/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2021-01-15 3:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 3:13 [PATCH v5 0/2] Synchronize user layer access with system PM ops and error handling Can Guo
2021-01-14 3:13 ` [PATCH v5 1/2] scsi: ufs: Fix a possible NULL pointer issue Can Guo
2021-01-14 3:13 ` [PATCH v5 2/2] scsi: ufs: Protect PM ops and err_handler from user access through sysfs Can Guo
2021-01-15 3:17 ` Martin K. Petersen [this message]
2021-01-21 3:34 ` [PATCH v5 0/2] Synchronize user layer access with system PM ops and error handling 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=yq1czy6sxd4.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 \
/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;
as well as URLs for NNTP newsgroup(s).