linux-kernel - Re: [RESEND PATCH] scsi: ufs: fix race between clock gating and devfreq scaling work

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Mon, 17 Oct 2016 17:13:56 -0700
From:   Subhash Jadavani <subhashj@...eaurora.org>
To:     "Martin K. Petersen" <martin.petersen@...cle.com>
Cc:     vinholikatti@...il.com, jejb@...ux.vnet.ibm.com,
        linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RESEND PATCH] scsi: ufs: fix race between clock gating and
 devfreq scaling work

On 2016-10-14 13:47, Martin K. Petersen wrote:
>>>>>> "Subhash" == Subhash Jadavani <subhashj@...eaurora.org> writes:
> 
> Subhash> UFS devfreq clock scaling work may require clocks to be ON if
> Subhash> it need to execute some UFS commands hence it may request for
> Subhash> clock hold before issuing the command. But if UFS clock gating
> Subhash> work is already running in parallel, ungate work would end up
> Subhash> waiting for the clock gating work to finish and as clock 
> gating
> Subhash> work would also wait for the clock scaling work to finish, we
> Subhash> would enter in deadlock state. Here is the call trace during
> Subhash> this deadlock state:
> 
> Somebody from the UFS camp, please review!

As there was no review so far, i have moved this patch as first patch in 
the new UFS bug fixes patch series ([PATCH v1 00/11] scsi: ufs: bug 
fixes patch series #1) sent by me today.

Thanks,
Subhash

-- 
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project