When calling "mount -t 9p -o trans=virtio foobar /mnt/bar" and foobar
exists in the current path, the 9p virtio transport driver will be
called with $CWD/foobar and fail with "9p: no channels available".
Similar problems exist with remote file servers
"mount -t 9p 23.42.08.15 /mnt/bar"
and Plan 9 From User Space applications
"mount -t 9p -o trans=unix,uname=$USER `namespace`/acme /mnt/bar"
A similar exception like for nfs, cifs and smbfs must be added for 9p.
Signed-off-by: Sven Eckelmann <sven.eckelmann@xxxxxx>
---
mount/mount.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/mount/mount.c b/mount/mount.c
index 84986e3..0eb0b0d 100644
--- a/mount/mount.c
+++ b/mount/mount.c
@@ -1797,7 +1797,8 @@ mount_one (const char *spec, const char *node, const char *types,
}
/* Handle possible LABEL= and UUID= forms of spec */
- if (types == NULL || (strncmp(types, "nfs", 3) &&
+ if (types == NULL || (strncmp(types, "9p", 2) &&
+ strncmp(types, "nfs", 3) &&
strncmp(types, "cifs", 4) &&
strncmp(types, "smbfs", 5))) {
nspec = spec_to_devname(spec);
--
1.7.2.3
--
To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
