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]

Date:	Wed, 27 Aug 2008 16:34:16 +0200
From:	Jörn Engel <joern@...fs.org>
To:	David Woodhouse <dwmw2@...radead.org>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	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>
Subject: Re: [PATCH 2/2][MTD] Add support for > 2GiB MTD devices

On Wed, 27 August 2008 10:01:32 +0100, David Woodhouse wrote:
> 
> True, and we'll definitely need a new MEMERASE64 ioctl. But for the
> _informational_ parts, those can happily be done through sysfs.

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.

So what was the reason again why mtd needs two userspace interfaces
instead of just one?

Jörn

-- 
It does not require a majority to prevail, but rather an irate,
tireless minority keen to set brush fires in people's minds.
-- Samuel Adams
--
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/