sctp: add SCTP_EXPOSE_POTENTIALLY_FAILED_STATE sockopt
authorXin Long <lucien.xin@gmail.com>
Fri, 8 Nov 2019 05:20:34 +0000 (13:20 +0800)
committerDavid S. Miller <davem@davemloft.net>
Fri, 8 Nov 2019 22:18:32 +0000 (14:18 -0800)
commit8d2a6935d842f12c25611b165eace778adb09a53
tree96fcfbf086db7a183aafeac719bb5a63a5dfd70e
parent768e15182dcb809e39c338290dda10c4e271d133
sctp: add SCTP_EXPOSE_POTENTIALLY_FAILED_STATE sockopt

This is a sockopt defined in section 7.3 of rfc7829: "Exposing
the Potentially Failed Path State", by which users can change
pf_expose per sock and asoc.

The new sockopt SCTP_EXPOSE_POTENTIALLY_FAILED_STATE is also
known as SCTP_EXPOSE_PF_STATE for short.

v2->v3:
  - return -EINVAL if params.assoc_value > SCTP_PF_EXPOSE_MAX.
  - define SCTP_EXPOSE_PF_STATE SCTP_EXPOSE_POTENTIALLY_FAILED_STATE.
v3->v4:
  - improve changelog.

Signed-off-by: Xin Long <lucien.xin@gmail.com>
Acked-by: Neil Horman <nhorman@tuxdriver.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
include/uapi/linux/sctp.h
net/sctp/socket.c