| 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: <1265411890-9156-1-git-send-email-maximlevitsky@gmail.com> Date: Sat, 6 Feb 2010 01:18:03 +0200 From: Maxim Levitsky <maximlevitsky@...il.com> To: David Woodhouse <dwmw2@...radead.org> Cc: "stanley.miao" <stanley.miao@...driver.com>, Vitaly Wool <vitalywool@...il.com>, Artem Bityutskiy <dedekind1@...il.com>, linux-mtd <linux-mtd@...ts.infradead.org>, linux-kernel <linux-kernel@...r.kernel.org> Subject: NAND: fixes This is part of my patcheset that touches the nand subsystem Stanley, patch #2 should now cover attempts to write outside the oob. Also I did another (don't know if less or more evil) approach to bad block testing. Now check_bad always takes the controller locks and selects the chip. Thus it is possible to use read_oob/write_oob. This however changes behavier of the nand_erase_nand to deny erases if any block within the range is bad. Also it selects/releases the chip once per erase block. This is done in patch #5. Patch #6 is ported to that change. Patches 1-3 are pure fixes. Best regards, Maxim Levitsky -- 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