Skip to content

net: Extend address label support

Petr Machata netdev 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest5 patches 8 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/5net: ipv4: Allow changing IPv4 labelsnet/ipv4/devinet.c+9 -10 replies
2/5net: ipv6: addrconf: Support IPv6 address labelsinclude/net/addrconf.h include/net/if_inet6.h net/ipv6/addrconf.c+15 -20 replies
3/5net: ipv6: addrconf: Expose IPv6 address labels through netlinknet/ipv6/addrconf.c+16 -20 replies
4/5selftests: rtnetlink: Make the set of tests to run configurabletools/testing/selftests/net/rtnetlink.sh+48 -420 replies
5/5selftests: rtnetlink: Add an address label testtools/testing/selftests/net/rtnetlink.sh+82 -00 replies

Reviews trailers per patch

All 5 patches have a Reviewed-by or Acked-by.

PatchIdo Schimmel
1/5R-b
2/5R-b
3/5R-b
4/5R-b
5/5R-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [PATCH net-next 0/5] net: Extend address label support

IPv4 addresses can be tagged with label strings. Unlike IPv6 addrlabels, which are used for prioritization of IPv6 addresses, these "ip address labels" are simply tags that the userspace can assign to IP addresses arbitrarily.

IPv4 has had support for these tags since before Linux was tracked in GIT. However it has never been possible to change the label after it is once defined. This limits usefulness of this feature. A userspace that wants to change a label might drop and recreate the address, but that disrupts routing and is just impractical.

IPv6 addresses lack support for address labels (in the sense of address tags) altogether.

In this patchset, extend IPv4 to allow changing the label defined at an address (in patch #1). Then, in patches #2 and #3, extend IPv6 with a suite of address label operations fully analogous with those defined for IPv4. Then in patches #4 and #5 add selftest coverage for the feature.

An example session with the feature in action:

	# ip address add dev d 2001:db8:1::1/64 label foo
	# ip address show dev d
	4: d: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc [...]
	    link/ether 06:29:74:fd:1f:eb brd ff:ff:ff:ff:ff:ff
	    inet6 2001:db8:1::1/64 scope global foo <--
	    valid_lft forever preferred_lft forever
	    inet6 fe80::429:74ff:fefd:1feb/64 scope link d
	    valid_lft forever preferred_lft forever
	# ip address replace dev d 2001:db8:1::1/64 label bar
	# ip address show dev d
	4: d: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc [...]
	    link/ether 06:29:74:fd:1f:eb brd ff:ff:ff:ff:ff:ff
	    inet6 2001:db8:1::1/64 scope global bar <--
	    valid_lft forever preferred_lft forever
	    inet6 fe80::429:74ff:fefd:1feb/64 scope link d
	    valid_lft forever preferred_lft forever
	# ip address del dev d 2001:db8:1::1/64 label foo
	RTNETLINK answers: Cannot assign requested address
	# ip address del dev d 2001:db8:1::1/64 label bar

Petr Machata (5):
net: ipv4: Allow changing IPv4 labels
net: ipv6: addrconf: Support IPv6 address labels
net: ipv6: addrconf: Expose IPv6 address labels through netlink
selftests: rtnetlink: Make the set of tests to run configurable
selftests: rtnetlink: Add an address label test

 include/net/addrconf.h                   |   2 +
 include/net/if_inet6.h                   |   1 +
 net/ipv4/devinet.c                       |  10 +-
 net/ipv6/addrconf.c                      |  30 +++-
 tools/testing/selftests/net/rtnetlink.sh | 172 +++++++++++++++++------
 5 files changed, 169 insertions(+), 46 deletions(-)
Signature · 1 line
2.39.0