mptcp: pm: in-kernel: rename 'add_addr_accept_max' to 'limit_add_addr_accepted'

A few variables linked to the in-kernel Path-Manager are confusing, and it would help current and future developers, to clarify them. One of them is 'add_addr_accept_max', which in fact represents the limit of ADD_ADDR that can be accepted: the limit set via 'ip mptcp limit add_addr_accepted X' for example. It is not linked to the maximum number of accepted ADD_ADDR. While at it, add an additional name for the corresponding variable in MPTCP INFO: mptcpi_limit_add_addr_accepted. Not to break the current uAPI, the new name is added as a 'define' pointing to the former name. This will then also help userspace devs. No functional changes intended.

Matthieu Baerts (NGI0) committed 1 year ago

Commit 37712d81 parent 45cae575 files · +21 −17Browse files

Showing the changes to include/uapi (1 of 5 files). Show all

Unified · Split

include/uapi/linux/mptcp.h+1−0

@@ -50,6 +50,7 @@ struct mptcp_info { · 49 unmodified lines
50	__u8 mptcpi_add_addr_signal_max;	50	__u8 mptcpi_add_addr_signal_max;
51	#define mptcpi_endp_signal_max mptcpi_add_addr_signal_max	51	#define mptcpi_endp_signal_max mptcpi_add_addr_signal_max
52	__u8 mptcpi_add_addr_accepted_max;	52	__u8 mptcpi_add_addr_accepted_max;
		53	#define mptcpi_limit_add_addr_accepted mptcpi_add_addr_accepted_max
53	__u32 mptcpi_flags;	54	__u32 mptcpi_flags;
54	__u32 mptcpi_token;	55	__u32 mptcpi_token;
55	__u64 mptcpi_write_seq;	56	__u64 mptcpi_write_seq;