From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: kernel-team@android.com, linux-scsi@vger.kernel.org,
rnayak@codeaurora.org, hongwus@codeaurora.org,
salyzyn@google.com, Can Guo <cang@codeaurora.org>,
saravanak@google.com, asutoshd@codeaurora.org,
nguyenb@codeaurora.org
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH v5 0/2] Synchronize user layer access with system PM ops and error handling
Date: Wed, 20 Jan 2021 22:34:38 -0500 [thread overview]
Message-ID: <161119996964.1307.5956597823766582436.b4-ty@oracle.com> (raw)
In-Reply-To: <1610594010-7254-1-git-send-email-cang@codeaurora.org>
On Wed, 13 Jan 2021 19:13:26 -0800, Can Guo wrote:
> This series contains two changes and it is based on 5.11/scsi-queue
> 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.
>
> Change since v4:
> - Incoroporate Adrian's comment - renamed ufshcd_is_sysfs_allowed() as ufshcd_is_user_access_allowed()
>
> [...]
Applied to 5.12/scsi-queue, thanks!
[1/2] scsi: ufs: Fix a possible NULL pointer issue
https://git.kernel.org/mkp/scsi/c/fb7afe24ba1b
[2/2] scsi: ufs: Protect PM ops and err_handler from user access through sysfs
https://git.kernel.org/mkp/scsi/c/9cd20d3f4736
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2021-01-21 3:57 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 ` [PATCH v5 0/2] Synchronize user layer access with system PM ops and error handling Martin K. Petersen
2021-01-21 3:34 ` Martin K. Petersen [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=161119996964.1307.5956597823766582436.b4-ty@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).