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:	Mon, 7 Jul 2008 10:40:27 +0200
From:	"Bart Van Assche" <bart.vanassche@...il.com>
To:	"Jinkai Gao" <mickeygjk@...il.com>
Cc:	linux-kernel@...r.kernel.org,
	"Arjan van de Ven" <arjan@...radead.org>
Subject: Re: Suggestion: LKM should be able to add system call for itself

On Mon, Jul 7, 2008 at 7:09 AM, Jinkai Gao <mickeygjk@...il.com> wrote:
> LKM(loadable kernel module) was first introduced for drivers. Users
> rarely need to talk to the modules directly. If does, several methods
> are available now, such as /proc file, interruption, etc. However,
> these interfaces are predefined, which makes the communication between
> user space and kernel space quite restricted.

Did you already have a look at e.g. http://lwn.net/Kernel/LDD3/ for
suggestions of alternatives for communication between userspace and
kernel modules ? Alternatives to system calls are e.g. ioctl's, memory
mapped I/O and sockets. The last alternative is used by udevd
(PF_NETLINK).

Bart.
--
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