[net-next 0/2] export SO_REUSEADDR and SO_REUSEPORT via sock_diag

[Jason Baron <jbaron@akamai.com>]

Hi,

We've found it useful to have SO_REUSEADDR and SO_REUSEPORT
available to understand when apps cannot bind() to specific
ports. I think this would be nice to have available as part
of monitoring tools as well. I can add this to 'ss' if this
series is accepted.

Thanks,

-Jason

Jason Baron (2):
  inet_diag: export SO_REUSEADDR and SO_REUSEPORT sockopts
  sock: add SO_REUSEADDR values to include/uapi/linux/socket.h

 drivers/block/drbd/drbd_receiver.c |  6 +++---
 drivers/scsi/iscsi_tcp.c           |  2 +-
 fs/ocfs2/cluster/tcp.c             |  2 +-
 include/linux/inet_diag.h          |  2 ++
 include/net/sock.h                 | 11 -----------
 include/uapi/linux/inet_diag.h     |  7 +++++++
 include/uapi/linux/socket.h        | 11 +++++++++++
 net/core/sock.c                    |  4 ++--
 net/ipv4/af_inet.c                 |  2 +-
 net/ipv4/inet_connection_sock.c    |  4 ++--
 net/ipv4/inet_diag.c               |  7 +++++++
 net/ipv4/tcp.c                     |  6 +++---
 net/ipv6/af_inet6.c                |  2 +-
 net/netfilter/ipvs/ip_vs_sync.c    |  2 +-
 net/rds/tcp_listen.c               |  2 +-
 net/sunrpc/svcsock.c               |  2 +-
 16 files changed, 44 insertions(+), 28 deletions(-)

-- 
2.25.1