diff options
| author | Juergen Gross <[email protected]> | 2023-01-30 12:30:35 +0100 |
|---|---|---|
| committer | Eric Van Hensbergen <[email protected]> | 2023-02-24 13:41:53 +0000 |
| commit | f1956f4ec15195ec60976d9b5625326285ab102e (patch) | |
| tree | b8108f3a834a34ab640a65f3102346bf807194e7 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 344504e912ea49033d012dad9de3f68e20c07634 (diff) | |
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/[email protected]
Fixes: 71ebd71921e4 ("xen/9pfs: connect to the backend")
Signed-off-by: Juergen Gross <[email protected]>
Reviewed-by: Simon Horman <[email protected]>
Signed-off-by: Dominique Martinet <[email protected]>
Signed-off-by: Eric Van Hensbergen <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions