9p: make cryptic unknown error from server less scary
authorEric Van Hensbergen <ericvh@opteron.9grid.us>
Sat, 3 May 2008 22:29:26 +0000 (17:29 -0500)
committerEric Van Hensbergen <ericvh@opteron.9grid.us>
Thu, 15 May 2008 00:23:26 +0000 (19:23 -0500)
Right now when we get an error string from the server that we can't
map we report a cryptic error that actually makes it look like we are
reporting a problem with the client.  This changes the text of the log
message to clarify where the error is coming from.

Signed-off-by: Eric Van Hensbergen <ericvh@gmail.com>
net/9p/error.c

index 388770c3631e4979a8cbcbd514f4a3a365195aa4..fdebe4314062c01e02636d5201a2068ee57a640c 100644 (file)
@@ -237,8 +237,8 @@ int p9_errstr2errno(char *errstr, int len)
        if (errno == 0) {
                /* TODO: if error isn't found, add it dynamically */
                errstr[len] = 0;
-               printk(KERN_ERR "%s: errstr :%s: not found\n", __func__,
-                      errstr);
+               printk(KERN_ERR "%s: server reported unknown error %s\n",
+                       __func__, errstr);
                errno = 1;
        }