netdev - Re: Generic netlink interface help

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:	Sun, 27 May 2007 15:24:56 +0200
From:	Johannes Berg <johannes@...solutions.net>
To:	Thomas Graf <tgraf@...g.ch>
Cc:	Samuel Ortiz <samuel@...tiz.org>, giometti@...eenne.com,
	netdev@...r.kernel.org
Subject: Re: Generic netlink interface help

On Sat, 2007-05-26 at 00:18 +0200, Thomas Graf wrote:

> This area is still work in progress but the basic idea is that
> like in kernel context, the application defines its set of
> commands and assigns message parsers for each command. 

Ok, but why? For when we get asynchronous events from the kernel?

> For now,
> the message parser is linked into the cache operations which
> means that you have to "update" a cache in order to use this
> feature. 

What's the cache good for to start with?

My current userland tool just send a message and expects back a
response. Obviously that's broken once we have events too, is that when
the message parsers come in?

johannes

Download attachment "signature.asc" of type "application/pgp-signature" (191 bytes)