From: Gorka guardiola <paurea@gmail.com>
To: 9fans@cse.psu.edu
Subject: [9fans] fids and so on
Date: Sat, 2 Jul 2005 16:02:40 +0200 [thread overview]
Message-ID: <599f06db0507020702542db12a@mail.gmail.com> (raw)
(I am having problems with the list and don't know if this message got through,
I am sorry if it did).
I am porting Recover to 4e. Recover is a filesystem which speaks
9P with two ends, a server and a client. When a connection falls down
it pushes the state and restarts the pending requests, so you don't
see a hung channel any more if your connection falls down.
I am now working on the authentification part. The problem I have is
that after doing the Tauth, I have to do the authentification RPC's
over the afid. auth_proxy would be just fine, except that it takes a
real file and does not speak 9P. I only have is a fid on a 9P
conversation.
I could use fauth, but then there would be no way to recover the fid
which I need for the attach later. I imagine four solutions for this:
First, which is what I would currently take rewrite auth_proxy to use
9Pread and 9Pwrite
which read and write from a fid using 9P over a connection.
The second would be to take out the system call fauth() which I dont like
and replace it with new one (fauth can be a library function) which
maps an fd with a fid so the kernel does the 9P talking. This may
require more changes for the attach, I don't know.
Third, writing a kernel filesystem, srvlike were you could post a
connection, give it a fid and get a file where you could read from.
Fourth, posting fids for file on /proc/xx/fd, this is the simplest
one, probably, though it requires changes all around.
What do you think about this?. What is the right approach?. Is there a
simpler way of doing this I have not thought of?.
TIA,
G.
--
- curiosity sKilled the cat
next reply other threads:[~2005-07-02 14:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-02 14:02 Gorka guardiola [this message]
2005-07-02 14:16 ` Christoph Lohmann
2005-07-02 23:47 ` Russ Cox
2005-07-04 9:23 Fco. J. Ballesteros
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=599f06db0507020702542db12a@mail.gmail.com \
--to=paurea@gmail.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).