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:	Thu, 28 Apr 2011 15:43:44 +0100
From:	Alan Cox <alan@...ux.intel.com>
To:	Greg KH <gregkh@...e.de>
Cc:	"Weil, Oren jer" <oren.jer.weil@...el.com>,
	Randy Dunlap <randy.dunlap@...cle.com>,
	"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"david@...dhou.se" <david@...dhou.se>
Subject: Re: [PATCH 6/8] staging/mei: Header file contain the Userland API,
 (IOCTL and its struct)

> Was this discussed in public?

Not much yet - but this is a staging driver so there is no defined ABI
and nothing is set in stone.

> > if someone has a good solution for that we are happy to hear it.
> 
> Did you rule out sysfs, configfs, netlink, etc.?

Pretty much. You need to create a handle, connect it to something and
perform transactions on it. Some of those must be serialized and they
have both input and output data, so they don't fit sysfs and friends.

It's effectively mostly a message passing system - the closest other
interface is the socket one but it doesn't really fit that and I don't
think Dave wants 'its got a connect sort of op so lets make it a socket
family' to be the device norm !

The identifier for the object is also long so doesn't work for a set of
devices by minor number either.

I think the more useful step is going to be some example user space as
that above all will show how it is intended to work

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ