From: Lorenzo Colitti <[email protected]> Date: Wed, 3 Aug 2016 09:58:09 +0900
> The problem is that the UID routing patches were never accepted > upstream, and because FRA_xxx and RTA_xxx are enums, there's no safe > way to add a new value out of tree like there would be with other > identifiers such as setsockopt values. > > I'm going to make another attempt to upstream the UID routing code > soon. If that doesn't make it, then we could attempt to reserve a > couple RTA_xxx and FRA_xxx values for local use. If upstream rejects the feature, it's because you'll be given a suggested alternative implementation in order to achieve your goals. In that respect, it is inappropriate to expect that we will "reserve" netlink ID space for such a feature that is rejected in that manner upstream.
