linux-kernel - Re: [patch/rfc 2.6.29 1/2] MTD: driver model updates

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:	Sat, 4 Apr 2009 09:17:46 -0700
From:	Kevin Cernekee <kpc.mtd@...il.com>
To:	David Woodhouse <dwmw2@...radead.org>
Cc:	dedekind@...radead.org, David Brownell <david-b@...bell.net>,
	Linux MTD <linux-mtd@...ts.infradead.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [patch/rfc 2.6.29 1/2] MTD: driver model updates

On 4/4/09, David Woodhouse <dwmw2@...radead.org> wrote:
> I really do think I want this to avoid the need for 64-bit ioctls
> (except maybe MEMERASE64).

So, after adding the sysfs patches, we have two remaining sets of MTD
operations that are limited to 32-bit offsets:

The first set is required to support >4GiB NAND devices: MEMERASE,
MEMREADOOB, and MEMWRITEOOB.

The second set might not make sense at all for most NAND devices:
MEMLOCK, MEMUNLOCK, and MEMGETREGIONINFO.  Maybe it would be nice to
extend them for consistency's sake, but it is possible that they will
never be needed on any >4GiB flash chip.

How would you like to handle these?  Any thoughts on what the
interfaces (sysfs or otherwise) might look like?

Thanks.
--
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/