linux-kernel - Re: [PATCH v6] mtd: handle partitioning on devices with 0 erasesize

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: <20170609231741.GP102137@google.com>
Date:   Fri, 9 Jun 2017 16:17:41 -0700
From:   Brian Norris <computersforpeace@...il.com>
To:     Chris Packham <chris.packham@...iedtelesis.co.nz>
Cc:     boris.brezillon@...e-electrons.com, linux-mtd@...ts.infradead.org,
        linux-kernel@...r.kernel.org, andrew@...n.ch,
        David Woodhouse <dwmw2@...radead.org>,
        Marek Vasut <marek.vasut@...il.com>,
        Richard Weinberger <richard@....at>,
        Cyrille Pitchen <cyrille.pitchen@...ev4u.fr>
Subject: Re: [PATCH v6] mtd: handle partitioning on devices with 0 erasesize

Thanks Chris!

On Fri, Jun 09, 2017 at 03:58:31PM +1200, Chris Packham wrote:
> erasesize is meaningful for flash devices but for SRAM there is no
> concept of an erase block so erasesize is set to 0. When partitioning
> these devices instead of ensuring partitions fall on erasesize
> boundaries we ensure they fall on writesize boundaries.
> 
> Helped-by: Boris Brezillon <boris.brezillon@...e-electrons.com>
> Signed-off-by: Chris Packham <chris.packham@...iedtelesis.co.nz>

Looks good to me. Did Boris have any last thoughts? Or else I'll merge
this.