linux-kernel - Re: intercommunications between Linux kernel modules

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] [day] [month] [year] [list]

Date:	Fri, 7 Oct 2011 12:41:35 -0500 (CDT)
From:	Christoph Lameter <cl@...two.org>
To:	Cyclonus J <cyclonusj@...il.com>
cc:	david@...g.hm, Andi Kleen <andi@...stfloor.org>,
	linux-kernel@...r.kernel.org
Subject: Re: intercommunications between Linux kernel modules

On Thu, 6 Oct 2011, Cyclonus J wrote:

> Yes, it is multi-threaded. I have two kernel modules and each of them will
> create its own kernel thread just for communication purpose (message passing).
>
> Do you know if there is any message primitves I can use to achieve this inside
> kernel?

F.e. Use the lockless lists in linux/include/llist.h?

Anything else will work too. Just declare a variable and access it from
both threads.

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