From: Pablo Neira <pablo@eurodev.net>
To: bikkit@gmail.com
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: Communication between kernel modules (what's the proper way?)
Date: Wed, 14 Sep 2005 02:11:33 +0200 [thread overview]
Message-ID: <43276AB5.8040008@eurodev.net> (raw)
In-Reply-To: <a60102c305091310302e9dc215@mail.gmail.com>
JC wrote:
> Somewhat out of topic for the mailing list, but I guess the developers
> here could advise me on the matter:
>
> I have developed two modules that use hooks to manipulate packets, and
> I wish for them to communicate with each other. The proper way to
> communicate with userspace is by using ioctls. But what is a proper
> way to use to pass data between the two modules, bearing in mind these
> are my modules and I cant apply for a system call...?
This isn't netfilter related at all, but it's related with kernel
programming.
You could do it by means of kernel notifiers (linux/notifier.h). You can
export a notifier_block that can be used to [un]register callbacks
(notifier_chain_[un]register) by both modules.
--
Pablo
prev parent reply other threads:[~2005-09-14 0:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 17:30 Communication between kernel modules (what's the proper way?) JC
2005-09-14 0:11 ` Pablo Neira [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43276AB5.8040008@eurodev.net \
--to=pablo@eurodev.net \
--cc=bikkit@gmail.com \
--cc=netfilter-devel@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.