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]
Date:   Mon, 28 May 2018 18:57:14 +0200
From:   Boris Brezillon <boris.brezillon@...tlin.com>
To:     Benjamin Lindqvist <benjamin.lindqvist@...ian.se>
Cc:     Stefan Agner <stefan@...er.ch>, Dmitry Osipenko <digetx@...il.com>,
        David Woodhouse <dwmw2@...radead.org>,
        Brian Norris <computersforpeace@...il.com>,
        Marek VaĊĦut <marek.vasut@...il.com>,
        robh+dt@...nel.org, mark.rutland@....com,
        Thierry Reding <thierry.reding@...il.com>,
        Michael Turquette <mturquette@...libre.com>, sboyd@...nel.org,
        Lucas Stach <dev@...xeye.de>,
        Miquel Raynal <miquel.raynal@...tlin.com>, richard@....at,
        Marcel Ziswiler <marcel@...wiler.com>, krzk@...nel.org,
        jonathanh@...dia.com, pdeschrijver@...dia.com,
        Prashant Gaikwad <pgaikwad@...dia.com>,
        Mirza Krak <mirza.krak@...il.com>,
        linux-mtd@...ts.infradead.org, linux-tegra@...r.kernel.org,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-clk@...r.kernel.org
Subject: Re: [PATCH v2 3/6] mtd: rawnand: add NVIDIA Tegra NAND Flash
 controller driver

On Mon, 28 May 2018 18:41:26 +0200
Benjamin Lindqvist <benjamin.lindqvist@...ian.se> wrote:

> Note that it's certainly possible to encode U-Boot and kernel with
> RS[4] and still use RS[8] for the rootfs even if the boot rom doesn't
> support it.

Not if you want to read/write from/to the uboot partition from Linux.

Per-partition ECC setup is not supported, so the only solutions we have
right now are:
1/ use the same ECC config as the one use by the bootrom
2/ only access uboot partition in raw mode from Linux (that implies
   generating images containing the ECC bytes so that they can be
   flashed to the device in raw mode)
3/ never access uboot partitions from Linux (not sure we want that)

> This whole 'use-bootable-ecc-only' business seems a bit
> overengineered.
> 

Hm, I don't find it over-engineered.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ