mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steve French <smfltc@us.ibm.com>
To: linux-kernel@vger.kernel.org
Subject: upcalls from kernel code to user space daemons
Date: 14 Jun 2004 13:07:48 -0500	[thread overview]
Message-ID: <1087236468.10367.27.camel@stevef95.austin.ibm.com> (raw)

Is there a good terse example of an upcall from a kernel module (such as
filesystem) to an optional user space helper daemon?   The NFS RPC
example seems more complicated than what I would like as does the
captive ioctl approach which I see in a few places.

I simply need to poke a userspace daemon (e.g. launched by mount) to do
in userspace these two optional functions which are not available in
kernel and pass a small (under 64K) amount of data back to the kernel
module:
1) getHostByName:  when the kernel cifs code detects a server crashes
and fails reconnecting the socket and the kernel code wants to see if
the hostname now has a new ip address.
2) package a kerberos ticket ala RFC2478 (SPNEGO)

And an only very loosely related question - 
The proc interface for returning debug information or stats is somewhat
awkward to use for returned data greater than about 1K - I had trouble
finding a good example of kernel code using /proc to return debug data
larger than that since it involves repeated calls into the pseudofile's
proc read function with careful setting of some offset/lengths which can
be hard when iterating through dynamically generated variable length
debug information.  Is there a good example of that?




             reply	other threads:[~2004-06-14 18:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-14 18:07 Steve French [this message]
2004-06-14 18:30 ` Chris Friesen
2004-06-14 21:40   ` Oliver Neukum
2004-06-14 21:57     ` Chris Friesen
2004-06-14 22:08       ` Bernd Petrovitsch
2004-06-14 22:22         ` Chris Friesen
2004-06-14 22:54           ` Tim Hockin
2004-06-14 23:10             ` Randy.Dunlap
2004-06-14 22:54     ` Steve French
2004-06-15  9:06       ` Oliver Neukum
2004-06-18 23:08 ` H. Peter Anvin

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=1087236468.10367.27.camel@stevef95.austin.ibm.com \
    --to=smfltc@us.ibm.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®