mirror of
https://github.com/openvswitch/ovs
synced 2025-08-31 14:25:26 +00:00
dpif-linux: Make dpif_linux_port_query_by_name() query only one datapath.
The kernel will report a vport with the given name in any datapath, but userspace only wants a vport with the given name in a specific datapath. Receiving information on a vport in an unexpected datapath yields bizarre and hard-to-debug problems. Bug #9889. Signed-off-by: Ben Pfaff <blp@nicira.com>
This commit is contained in:
@@ -418,9 +418,15 @@ dpif_linux_port_query__(const struct dpif *dpif, uint32_t port_no,
|
||||
|
||||
error = dpif_linux_vport_transact(&request, &reply, &buf);
|
||||
if (!error) {
|
||||
dpif_port->name = xstrdup(reply.name);
|
||||
dpif_port->type = xstrdup(netdev_vport_get_netdev_type(&reply));
|
||||
dpif_port->port_no = reply.port_no;
|
||||
if (reply.dp_ifindex != request.dp_ifindex) {
|
||||
/* A query by name reported that 'port_name' is in some datapath
|
||||
* other than 'dpif', but the caller wants to know about 'dpif'. */
|
||||
error = ENODEV;
|
||||
} else {
|
||||
dpif_port->name = xstrdup(reply.name);
|
||||
dpif_port->type = xstrdup(netdev_vport_get_netdev_type(&reply));
|
||||
dpif_port->port_no = reply.port_no;
|
||||
}
|
||||
ofpbuf_delete(buf);
|
||||
}
|
||||
return error;
|
||||
|
Reference in New Issue
Block a user