From: Oliver Neukum <oliver@neukum.org>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: Steve French <smfltc@us.ibm.com>, linux-kernel@vger.kernel.org
Subject: Re: upcalls from kernel code to user space daemons
Date: Mon, 14 Jun 2004 23:40:58 +0200 [thread overview]
Message-ID: <200406142341.13340.oliver@neukum.org> (raw)
In-Reply-To: <40CDEECF.7060102@nortelnetworks.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> > 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.
Is that possible at all? It looks like that might deadlock in the page
out code path.
> > 2) package a kerberos ticket ala RFC2478 (SPNEGO)
>
> One way to do it (or is this what you meant by captive ioctl?)
>
> userspace daemon loops on ioctl()
> kernel portion of ioctl call goes to sleep until something to do
> when needed, fill in data and return to userspace
> userspace does stuff, then passes data back down via ioctl()
> ioctl() puts userspace back to sleep and continues on with other work
You could just as well implement an ordinary read()
Regards
Oliver
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAzhtxbuJ1a+1Sn8oRAvupAJ0T6K8PMeKwWanDTHUmeYtpmsPnKQCeLZbk
cZC0HjRPQSN3Xmkp1tSKFIA=
=tZMS
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-06-14 21:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 18:07 Steve French
2004-06-14 18:30 ` Chris Friesen
2004-06-14 21:40 ` Oliver Neukum [this message]
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=200406142341.13340.oliver@neukum.org \
--to=oliver@neukum.org \
--cc=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=smfltc@us.ibm.com \
/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®