linux-kernel - Re: Existing netlink kernel <--> kernel communication

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

Message-Id: <1250543073.30166.100.camel@localhost.localdomain>
Date:	Mon, 17 Aug 2009 14:04:33 -0700
From:	Marcel Holtmann <marcel@...tmann.org>
To:	"Luis R. Rodriguez" <mcgrof@...il.com>
Cc:	linux-kernel@...r.kernel.org, Kevin Hayes <kevin@...eros.com>,
	Jouni Malinen <j@...fi>,
	Johannes Berg <johannes@...solutions.net>
Subject: Re: Existing netlink kernel <--> kernel communication

Hi Luis,

> Was curious if there are existing use cases of netlink for kernel <-->
> kernel communication rather than the typical kernel <--> userspace.
> The original RFC 3549 [1] does specify it could have been used for
> "intra-kernel messaging", but am just not aware of existing use cases.
> A pointer could help.

I would use direct function calls for kernel to kernel communication. No
need to put any messaging system in between.

Regards

Marcel


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