linux-kernel - Re: [PATCH] mtd: spi-nor: fix erase_type array to indicate current map conf

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:   Fri, 23 Nov 2018 12:39:44 +0000
From:   <Tudor.Ambarus@...rochip.com>
To:     <alexander.sverdlin@...ia.com>, <marek.vasut@...il.com>,
        <dwmw2@...radead.org>, <computersforpeace@...il.com>,
        <boris.brezillon@...tlin.com>, <richard@....at>
CC:     <linux-mtd@...ts.infradead.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] mtd: spi-nor: fix erase_type array to indicate current
 map conf

Hi, Alexander,

On 11/23/2018 01:33 PM, Sverdlin, Alexander (Nokia - DE/Ulm) wrote:
> So erasesize is back to the value before non-uniform support patches,
> partitions are not made read only any more, but actual write or
> erase still fails.

How does the erase fail?

What map configuration is selected? Where are the hybrid blocks, at the bottom
or at the top of the address space?

Does the erase fail even when address is aligned with 64k and the size multiple
of 64k? Does the following fail?

$ mtd_debug erase /dev/your_mtd 0 65536

The non-uniform erase will fail if it can't select a sequence of commands that
can erase the entire requested chunk.

Cheers,
ta