Re: [PATCH 2/2] virnetdevopenvswitch: Try to unescape ovs-vsctl reply in one specific case

2020-12-17 Thread Michal Privoznik
On 12/16/20 8:17 PM, Laine Stump wrote: On 12/16/20 1:45 PM, Michal Privoznik wrote: During testing of my patch v6.10.0-rc1~221 it was found that    'ovs-vsctl get Interface $name name' or    'ovs-vsctl find Interface options:vhost-server-path=$path' may return a string in double quotes, e.g.

Re: [PATCH 2/2] virnetdevopenvswitch: Try to unescape ovs-vsctl reply in one specific case

2020-12-16 Thread Laine Stump
On 12/16/20 1:45 PM, Michal Privoznik wrote: During testing of my patch v6.10.0-rc1~221 it was found that 'ovs-vsctl get Interface $name name' or 'ovs-vsctl find Interface options:vhost-server-path=$path' may return a string in double quotes, e.g. "vhost-user1". Later investigation of

[PATCH 2/2] virnetdevopenvswitch: Try to unescape ovs-vsctl reply in one specific case

2020-12-16 Thread Michal Privoznik
During testing of my patch v6.10.0-rc1~221 it was found that 'ovs-vsctl get Interface $name name' or 'ovs-vsctl find Interface options:vhost-server-path=$path' may return a string in double quotes, e.g. "vhost-user1". Later investigation of openvswitch code showed, that early versions (like