9p/xen: fix version parsing
authorJuergen Gross <jgross@suse.com>
Mon, 30 Jan 2023 11:30:35 +0000 (12:30 +0100)
committerEric Van Hensbergen <ericvh@kernel.org>
Fri, 24 Feb 2023 13:41:53 +0000 (13:41 +0000)
commitf1956f4ec15195ec60976d9b5625326285ab102e
treeb8108f3a834a34ab640a65f3102346bf807194e7
parent344504e912ea49033d012dad9de3f68e20c07634
9p/xen: fix version parsing

When connecting the Xen 9pfs frontend to the backend, the "versions"
Xenstore entry written by the backend is parsed in a wrong way.

The "versions" entry is defined to contain the versions supported by
the backend separated by commas (e.g. "1,2"). Today only version "1"
is defined. Unfortunately the frontend doesn't look for "1" being
listed in the entry, but it is expecting the entry to have the value
"1".

This will result in failure as soon as the backend will support e.g.
versions "1" and "2".

Fix that by scanning the entry correctly.

Link: https://lkml.kernel.org/r/20230130113036.7087-2-jgross@suse.com
Fixes: 71ebd71921e4 ("xen/9pfs: connect to the backend")
Signed-off-by: Juergen Gross <jgross@suse.com>
Reviewed-by: Simon Horman <simon.horman@corigine.com>
Signed-off-by: Dominique Martinet <asmadeus@codewreck.org>
Signed-off-by: Eric Van Hensbergen <ericvh@kernel.org>
net/9p/trans_xen.c