diff options
| author | kvik <kvik@a-b.xyz> | 2020-08-01 15:27:28 +0200 |
|---|---|---|
| committer | kvik <kvik@a-b.xyz> | 2020-08-01 15:27:28 +0200 |
| commit | e5894dcceaedeaf7d4f5537dd306170b1b6d4814 (patch) | |
| tree | 1cc00acf23373f15f69218ba1ccbb372a9cb3899 /sys/src/cmd/plumb | |
| parent | 88a468f205af2bfdaa015a5bc33424ae0d56de08 (diff) | |
pre-lib9p servers: fix incorrect Tversion handling
version(5) says:
If the server does not understand the client's version
string, it should respond with an Rversion message (not
Rerror) with the version string the 7 characters
``unknown''.
Pre-lib9p file servers -- all except cwfs(4) -- do return Rerror.
lib9p(2) follows the above spec, although ignoring the next part
concerning comparison after period-stripping. It assumes an
Fcall.version starting with "9P" is correctly formed and returns
the only supported version of the protocol, which seems alright.
This patch brings pre-lib9p servers in accordance with the spec.
Diffstat (limited to 'sys/src/cmd/plumb')
| -rw-r--r-- | sys/src/cmd/plumb/fsys.c | 9 |
1 files changed, 4 insertions, 5 deletions
diff --git a/sys/src/cmd/plumb/fsys.c b/sys/src/cmd/plumb/fsys.c index 92764d248..e79ea5c31 100644 --- a/sys/src/cmd/plumb/fsys.c +++ b/sys/src/cmd/plumb/fsys.c @@ -563,11 +563,10 @@ fsysversion(Fcall *t, uchar *buf, Fid*) if(t->msize < messagesize) messagesize = t->msize; t->msize = messagesize; - if(strncmp(t->version, "9P2000", 6) != 0){ - fsysrespond(t, buf, "unrecognized 9P version"); - return t; - } - t->version = "9P2000"; + if(strncmp(t->version, "9P", 2) != 0) + t->version = "unknown"; + else + t->version = "9P2000"; fsysrespond(t, buf, nil); return t; } |