linux-kernel - Re: [patch 2/5] Staging: vme: add VME userspace driver

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 10 Aug 2009 22:05:26 +0200
From:	"Emilio G. Cota" <cota@...ap.org>
To:	Greg KH <gregkh@...e.de>
Cc:	Martyn Welch <martyn.welch@...anuc.com>,
	linux-kernel@...r.kernel.org, devel@...uxdriverproject.org,
	Sebastien Dugue <sebastien.dugue@...l.net>
Subject: Re: [patch 2/5] Staging: vme: add VME userspace driver

Greg KH wrote:
> On Sun, Aug 09, 2009 at 02:17:16PM +0200, Emilio G. Cota wrote:
> > > Instead of using that we implemented a heretic IOCTL-based
> > > interface for user-space; at least with it you could create a
> > > driver (with no interrupt support) for a device in user-space.
> 
> Why not just use the UIO interface instead of creating
> yet-another-kernel/user-api?
> 
> Will that interface not work for what you want to use here?

Certainly. I didn't mean we'd like to see that merged. Currently
we make extensive use of IOCTLs because we are maintaining
kernel and user-space code for two platforms/OSes (ppc-lynx and
x86-linux), and not having access to lynx' source code doesn't
help. So IOCTLs are pretty much everywhere, much to my regret.

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