linux-kernel - Re: NAND: fixes

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]

Message-ID: <1265650862.4115.1.camel@maxim-laptop>
Date:	Mon, 08 Feb 2010 19:41:02 +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: Re: NAND: fixes

On Sat, 2010-02-06 at 01:18 +0200, Maxim Levitsky wrote: 
> 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

Any update?

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/