[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f41c45d5b151ca98da1e41848c067f89@codeaurora.org>
Date: Sat, 12 Jun 2021 15:13:28 +0800
From: Can Guo <cang@...eaurora.org>
To: Bart Van Assche <bvanassche@....org>
Cc: asutoshd@...eaurora.org, nguyenb@...eaurora.org,
hongwus@...eaurora.org, ziqichen@...eaurora.org,
linux-scsi@...r.kernel.org, kernel-team@...roid.com,
Alim Akhtar <alim.akhtar@...sung.com>,
Avri Altman <avri.altman@....com>,
"James E.J. Bottomley" <jejb@...ux.ibm.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
Adrian Hunter <adrian.hunter@...el.com>,
Bean Huo <beanhuo@...ron.com>,
Stanley Chu <stanley.chu@...iatek.com>,
Keoseong Park <keosung.park@...sung.com>,
Jaegeuk Kim <jaegeuk@...nel.org>,
Dinghao Liu <dinghao.liu@....edu.cn>,
"Gustavo A. R. Silva" <gustavoars@...nel.org>,
Kiwoong Kim <kwmad.kim@...sung.com>,
Satya Tangirala <satyat@...gle.com>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 9/9] scsi: ufs: Apply more limitations to user access
On 2021-06-12 05:03, Bart Van Assche wrote:
> On 6/9/21 9:43 PM, Can Guo wrote:
>> Do not let user access HW if hba resume fails or hba is not in good
>> state,
>> otherwise it may lead to various stability issues.
>
> Just like for the previous patch, I'm wondering whether or not such a
> failure perhaps indicates a hardware bug?
>
Indeed yes, but user access happens when power/clock is not ready will
lead to system stability issues, e.g., OCP or unclocked register access.
Nowadays, customers are heavily using UFS sysfs nodes during runtime,
so our test teams added quite a lot test scripts to simulate user access
to UFS sysfs nodes during their test.
Thanks,
Can Guo.
> Thanks,
>
> Bart.
Powered by blists - more mailing lists