linux-kernel - Re: [PATCH v2 2/2] scsi: ufs: Execute START_STOP

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]

Message-ID: <CAE=gft4iB_iHfZ10vtty1aC6BAevT_zGLd0Yh3P8=Cpg4pymew@mail.gmail.com>
Date:   Fri, 28 Sep 2018 16:09:28 -0700
From:   Evan Green <evgreen@...omium.org>
To:     hch@...radead.org
Cc:     Vinayak Holikatti <vinholikatti@...il.com>,
        jejb@...ux.vnet.ibm.com, martin.petersen@...cle.com,
        adrian.hunter@...el.com, stanislav.nijnikov@....com,
        linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org,
        Doug Anderson <dianders@...omium.org>,
        Gwendal Grignou <gwendal@...omium.org>
Subject: Re: [PATCH v2 2/2] scsi: ufs: Execute START_STOP_UNIT during init

On Fri, Sep 28, 2018 at 4:04 PM Christoph Hellwig <hch@...radead.org> wrote:
>
> On Fri, Sep 28, 2018 at 04:02:03PM -0700, Evan Green wrote:
> > For UFS devices that are provisioned to have an initial power mode
> > (bInitPowerMode) of "sleep", Linux will currently fail to enumerate
> > the device. This is because the UFS specification says that the
> > device must get a START_STOP_UNIT SCSI command to wake the unit
> > up before other common initialization features like the device
> > descriptor will be available to be read.
>
> Yikes, this is just completely broken in terms of scsi compliance.
>
> I think we should simply not support such devices.

Really? It's part of the UFS spec. The document I have specifies that
I shouldn't reproduce without permission, but it's in JESD220A section
7.2.4 UFS-Sleep Power Mode.
-Evan