linux-kernel - Re: [PATCH 2/2][MTD] Add support for

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]

Message-ID: <Pine.LNX.4.64.0808271243200.3610@t2.domain.actdsltmp>
Date:	Wed, 27 Aug 2008 12:44:35 -0700 (PDT)
From:	Trent Piepho <tpiepho@...escale.com>
To:	Artem Bityutskiy <dedekind@...radead.org>
cc:	Jörn Engel <joern@...fs.org>,
	linux-mtd-bounces@...ts.infradead.org,
	"'Bruce Leonard'" <brucle@...thlink.net>, Bruce_Leonard@...inc.com,
	linux-kernel@...r.kernel.org, Tim Anderson <tanderson@...sta.com>,
	linux-mtd@...ts.infradead.org,
	"'Andrew Morton'" <akpm@...ux-foundation.org>,
	David Woodhouse <dwmw2@...radead.org>,
	Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [PATCH 2/2][MTD] Add support for > 2GiB MTD devices

On Wed, 27 Aug 2008, Artem Bityutskiy wrote:
> > On Wed, 2008-08-27 at 16:34 +0200, Jörn Engel wrote:
> > They certainly can, but should they?  There may be some reason to prefer
> > sysfs that should be self-evident - except that I'm a bit thick and seem
> > to need it spelled out.  Or maybe I've just become disillusioned with
> > the practice of replacing crappy interfaces (ioctl here) with other
> > crappy interfaces (sysfs here) and having to support both for all
> > eternity.  sysctl, ioctl, proc, sysfs, debugfs, netlink, ... -
> > individually they all suck in their own peculiar way.  But together they
> > create a mess I no longer dare to name.
> 
> The plus of sysfs I see is that I can add more files to expose more
> information in sysfs, while I can not change MEMGETINFO ioctl. E.g., I
> need to expose sub-page size to user-space, and I cannot do this with
> MEMGETINFO.

You can do this with ioctls, if you designed them with extra space and
versioning from the beginning.