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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20180928230416.GA30772@infradead.org>
Date:   Fri, 28 Sep 2018 16:04:16 -0700
From:   Christoph Hellwig <hch@...radead.org>
To:     Evan Green <evgreen@...omium.org>
Cc:     Vinayak Holikatti <vinholikatti@...il.com>,
        "James E.J. Bottomley" <jejb@...ux.vnet.ibm.com>,
        "Martin K. Petersen" <martin.petersen@...cle.com>,
        Adrian Hunter <adrian.hunter@...el.com>,
        Stanislav Nijnikov <stanislav.nijnikov@....com>,
        linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org,
        Douglas 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 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.