linux-kernel - RE: [PATCH v2] drivers:mtd:spi-nor:checkup FSR error bits

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

Date:   Mon, 4 Dec 2017 13:27:43 +0000
From:   "Bean Huo (beanhuo)" <beanhuo@...ron.com>
To:     Cyrille Pitchen <cyrille.pitchen@...ev4u.fr>
CC:     "linux-mtd@...ts.infradead.org" <linux-mtd@...ts.infradead.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v2] drivers:mtd:spi-nor:checkup FSR error bits

Hi, Cyrille

>Hi Bean,
>
>Le 04/12/2017 à 13:34, Bean Huo (beanhuo) a écrit :
>> For Micron spi nor device, when erase/program operation fails,
>> especially the failure results from intending to modify protected
>> space, spi-nor upper layers still get the return which shows the
>> operation succeeds. This is because current spi_nor_fsr_ready() only
>> uses FSR bit.7 (flag status register) to check device whether ready.
>> This patch fixs this issue by checking relevant error
>
>s/fixs/fixes/
>
>> bits in FSR.
>> The FSR is a powerful tool to investigate the staus of
>
>s/staus/status/
>
>> device, checking information regarding what is actually doing the
>> memory and detecting possible error conditions.
>>
>> Signed-off-by: beanhuo <beanhuo@...ron.com>
>
>Otherwise,
>Acked-by: Cyrille Pitchen <cyrille.pitchen@...ev4u.fr>
>
>No need to resend, I'll fix these tiny issues myself :)
>

Thanks!

// Bean Huo