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
| ||
|
Message-ID: <20140913173841.GA18093@brian-ubuntu> Date: Sat, 13 Sep 2014 10:38:41 -0700 From: Brian Norris <computersforpeace@...il.com> To: Huang Shijie <shijie8@...il.com> Cc: Boris BREZILLON <boris.brezillon@...e-electrons.com>, Huang Shijie <shijie.huang@...el.com>, Mike Voytovich <mvoytovich@...pal.com>, linux-kernel@...r.kernel.org, Huang Shijie <b32955@...escale.com>, linux-mtd@...ts.infradead.org, Roy Lee <roylee@...pal.com>, David Woodhouse <dwmw2@...radead.org>, linux-arm-kernel@...ts.infradead.org Subject: Re: [PATCH] mtd: nand: gpmi: add proper raw access support On Sat, Sep 13, 2014 at 11:36:24PM +0800, Huang Shijie wrote: > On Fri, Sep 12, 2014 at 02:30:50PM +0200, Boris BREZILLON wrote: > > This test validates what's returned by ecc_strength file in sysfs > > (which in turn is specified by the NAND controller when initializing > > the NAND chip). > > > > Doing this should not imply knowing the ECC algorithm in use in the > > NAND controller or the layout used to store data on NAND. > the difficulty is that the ECC parity area can be not byte aligned. Is there a problem with just rounding up to the nearest byte alignment and ignoring the few bits that are wasted? > As I ever said, it is hard to implement the two hooks. "Hard" doesn't mean we shouldn't. I really would like to encourage more NAND drivers to be programmed against the expected MTD behavior -- that (if possible with the given hardware) they can pass the MTD tests (drivers/mtd/tests/*). Brian -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists