netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Dumazet <edumazet@google.com>
To: "David S . Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	 Paolo Abeni <pabeni@redhat.com>
Cc: David Ahern <dsahern@kernel.org>,
	netdev@vger.kernel.org, eric.dumazet@gmail.com,
	 Eric Dumazet <edumazet@google.com>
Subject: [PATCH net-next 0/8] inet: more data-race fixes
Date: Thu, 21 Sep 2023 13:30:13 +0000	[thread overview]
Message-ID: <20230921133021.1995349-1-edumazet@google.com> (raw)

This series fixes some existing data-races on inet fields:

inet->mc_ttl, inet->pmtudisc, inet->tos, inet->uc_index,
inet->mc_index and inet->mc_addr.

While fixing them, we convert eight socket options
to lockless implementation.

Eric Dumazet (8):
  inet: implement lockless IP_MULTICAST_TTL
  inet: implement lockless IP_MTU_DISCOVER
  inet: implement lockless IP_TOS
  inet: lockless getsockopt(IP_OPTIONS)
  inet: lockless getsockopt(IP_MTU)
  inet: implement lockless getsockopt(IP_UNICAST_IF)
  inet: lockless IP_PKTOPTIONS implementation
  inet: implement lockless getsockopt(IP_MULTICAST_IF)

 include/net/ip.h                              |  14 +-
 net/dccp/ipv4.c                               |   2 +-
 net/ipv4/datagram.c                           |   6 +-
 net/ipv4/inet_diag.c                          |   2 +-
 net/ipv4/ip_output.c                          |  13 +-
 net/ipv4/ip_sockglue.c                        | 192 ++++++++----------
 net/ipv4/ping.c                               |   8 +-
 net/ipv4/raw.c                                |  19 +-
 net/ipv4/tcp_ipv4.c                           |   9 +-
 net/ipv4/udp.c                                |  18 +-
 net/mptcp/sockopt.c                           |   8 +-
 net/netfilter/ipvs/ip_vs_sync.c               |   4 +-
 net/sctp/protocol.c                           |   4 +-
 .../selftests/net/mptcp/mptcp_connect.sh      |   2 +-
 14 files changed, 147 insertions(+), 154 deletions(-)

-- 
2.42.0.459.ge4e396fd5e-goog


             reply	other threads:[~2023-09-21 17:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-21 13:30 Eric Dumazet [this message]
2023-09-21 13:30 ` [PATCH net-next 1/8] inet: implement lockless IP_MULTICAST_TTL Eric Dumazet
2023-09-21 19:03   ` David Ahern
2023-09-21 13:30 ` [PATCH net-next 2/8] inet: implement lockless IP_MTU_DISCOVER Eric Dumazet
2023-09-21 19:03   ` David Ahern
2023-09-21 13:30 ` [PATCH net-next 3/8] inet: implement lockless IP_TOS Eric Dumazet
2023-09-21 19:10   ` David Ahern
2023-09-21 19:15     ` Eric Dumazet
2023-09-21 13:30 ` [PATCH net-next 4/8] inet: lockless getsockopt(IP_OPTIONS) Eric Dumazet
2023-09-21 19:12   ` David Ahern
2023-09-21 13:30 ` [PATCH net-next 5/8] inet: lockless getsockopt(IP_MTU) Eric Dumazet
2023-09-21 19:13   ` David Ahern
2023-09-21 13:30 ` [PATCH net-next 6/8] inet: implement lockless getsockopt(IP_UNICAST_IF) Eric Dumazet
2023-09-21 19:19   ` David Ahern
2023-09-21 13:30 ` [PATCH net-next 7/8] inet: lockless IP_PKTOPTIONS implementation Eric Dumazet
2023-09-21 19:23   ` David Ahern
2023-09-21 13:30 ` [PATCH net-next 8/8] inet: implement lockless getsockopt(IP_MULTICAST_IF) Eric Dumazet
2023-09-21 19:24   ` David Ahern

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=20230921133021.1995349-1-edumazet@google.com \
    --to=edumazet@google.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=eric.dumazet@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).