From: Jason Baron <jbaron@akamai•com>
To: davem@davemloft•net, dsahern@kernel•org, edumazet@google•com,
kuba@kernel•org, pabeni@redhat•com
Cc: netdev@vger•kernel.org
Subject: [net-next 0/2] export SO_REUSEADDR and SO_REUSEPORT via sock_diag
Date: Tue, 12 Sep 2023 10:31:47 -0400 [thread overview]
Message-ID: <cover.1694523876.git.jbaron@akamai.com> (raw)
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
next reply other threads:[~2023-09-12 15:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 14:31 Jason Baron [this message]
2023-09-12 14:31 ` [net-next 1/2] inet_diag: export SO_REUSEADDR and SO_REUSEPORT sockopts Jason Baron
2023-09-12 16:26 ` Kuniyuki Iwashima
2023-09-12 18:54 ` Jason Baron
2023-09-12 14:31 ` [net-next 2/2] sock: add SO_REUSEADDR values to include/uapi/linux/socket.h Jason Baron
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1694523876.git.jbaron@akamai.com \
--to=jbaron@akamai$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=dsahern@kernel$(echo .)org \
--cc=edumazet@google$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox