From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Attach/Auth
Date: Tue, 27 Aug 2002 08:35:21 +0200 [thread overview]
Message-ID: <20020827083520.W29921@cackle.proxima.alt.za> (raw)
In-Reply-To: <20020827070622.V29921@cackle.proxima.alt.za>; from Lucio De Re on Tue, Aug 27, 2002 at 07:06:23AM +0200
On Tue, Aug 27, 2002 at 07:06:23AM +0200, Lucio De Re wrote:
>
> which is followed by a puzzling Tattach exchange:
>
> <-4- Tattach tag 13 fid 349 afid 333 uname lucio aname
> -4-> Rerror tag 13 ename unknown fid
>
> I assume the "unknown fid" comes from srv() which I don't quite
> understand.
>
The following code in /sys/src/lib9p/srv.c is suspicious:
case Tauth:
if((r->fid = allocfid(srv->fpool, r->ifcall.fid)) == nil){
respond(r, Edupfid);
break;
}
r->afid = nil;
if(r->ifcall.afid != NOFID && (r->afid = allocfid(srv->fpool, r->ifcall.fid)) == nil){
respond(r, Eunknownfid);
break;
}
The second allocfid() seems to work a lot better if replaced by:
lookupfid(srv->fpool, r->ifcall.afid)
The Tattach exchange now looks like:
<-4- Tattach tag 11 fid 324 afid 339 uname lucio aname
-4-> Rattach tag 11 qid (0000000000000000 0 d)
which seems a little healthier except for the Qid value, which
repeats the value that was assigned to the auth file.
++L
next prev parent reply other threads:[~2002-08-27 6:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-26 23:24 Russ Cox
2002-08-27 5:06 ` Lucio De Re
2002-08-27 6:35 ` Lucio De Re [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-30 3:10 Russ Cox
2002-08-30 3:38 ` Roman V. Shaposhnick
2002-08-30 3:41 ` Alexander Viro
2002-08-28 10:45 Russ Cox
2002-08-30 2:58 ` Roman V. Shaposhnick
2002-08-28 9:24 Charles Forsyth
2002-08-27 12:25 Russ Cox
2002-08-28 6:15 ` Roman V. Shaposhnick
2002-08-27 11:25 Russ Cox
2002-08-27 11:54 ` Lucio De Re
2002-08-26 14:02 Lucio De Re
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=20020827083520.W29921@cackle.proxima.alt.za \
--to=lucio@proxima.alt.za \
--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).