Re: [PATCH] net: switchdev: restrict vid range abstraction

From: David Miller
Date: Wed Jul 29 2015 - 14:28:49 EST


From: Scott Feldman <sfeldma@xxxxxxxxx>
Date: Wed, 29 Jul 2015 00:31:44 -0700

> Since the netlink request (for example vlan add) includes the range,
> I'm not seeing how we can response with success for the satisfied
> vlans in the range, and also respond with an error for the unsatisfied
> vlans in the range. In other words, from the netlink msgs
> perspective, we need to treat a vlan range as all-or-nothing. So in
> your example, if hw can't add vlan 2, we fail the entire request to
> add range 2-5. This is where the prepare phase checks to make sure
> the entire request can be satisfied before committing to hw.

This was my concern with the change as well.

The user asked for the range to be installed, so if any portion
of it cannot be done we must not make any changes to the HW
configuration and fail the entire request.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/