linux-kernel - RE: Adding subpage support to NAND driver -- backwards compatibility concerns

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:	Fri, 24 Apr 2015 09:13:24 +1000
From:	Iwo Mergler <Iwo.Mergler@...commwireless.com>
To:	Richard Weinberger <richard@....at>, Josh Cartwright <joshc@...com>
CC:	Ben Shelton <ben.shelton@...com>,
	"dwmw2@...radead.org" <dwmw2@...radead.org>,
	"computersforpeace@...il.com" <computersforpeace@...il.com>,
	"dedekind1@...il.com" <dedekind1@...il.com>,
	"adrian.hunter@...el.com" <adrian.hunter@...el.com>,
	"linux-mtd@...ts.infradead.org" <linux-mtd@...ts.infradead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"punnaiah.choudary.kalluri@...inx.com" 
	<punnaiah.choudary.kalluri@...inx.com>,
	"xander.huff@...com" <xander.huff@...com>
Subject: RE: Adding subpage support to NAND driver -- backwards
 compatibility concerns

On Fri, 24 Apr 2015 05:30:55 +1000
Richard Weinberger <richard@....at> wrote:

> Am 23.04.2015 um 20:39 schrieb Josh Cartwright:

> > Is there no metadata in the UBI data structures in flash that
> > indicate the min IO boundary?  Assuming no, is another option to,
> > at the time of attach, try both the min IO access size, and, if
> > that doesn't work, try the page size?
> 
> Correct. UBI has no information about that.
> If you add subpage support to the driver I'd make it opt-in such that
> existing setups won't break.

I'm wondering, given that EC headers contain vid header offset
and data offset fields, shouldn't UBI be able to deduce at attach
time what the relevant parameters are on a partition?

Something along the lines of using the parameters of the first
PEB with valid EC header, then balking if another EC header is
encountered with different info. As long as MTD allows the
so deduced minimum access size, it seems safe.

This could help enormously in situations like this, where
MTD drivers experience sudden bursts of improvement.


Best regards,

Iwo
--
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/