netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Eric Dumazet <edumazet@google.com>
Cc: "David S . Miller" <davem@davemloft.net>,
	Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org, Kuniyuki Iwashima <kuniyu@amazon.com>,
	Simon Horman <horms@kernel.org>,
	eric.dumazet@gmail.com
Subject: Re: [PATCH net 00/16] net: first round to use dev_net_rcu()
Date: Sat, 1 Feb 2025 18:18:01 -0800	[thread overview]
Message-ID: <20250201181801.4427248a@kernel.org> (raw)
In-Reply-To: <20250131171334.1172661-1-edumazet@google.com>

On Fri, 31 Jan 2025 17:13:18 +0000 Eric Dumazet wrote:
>   ipv4: use RCU protection in inet_select_addr()

patchwork thinks it's an incomplete series due to lack of this patch 
on the list. I'm afraid a repost will be needed :(
-- 
pw-bot: cr

  parent reply	other threads:[~2025-02-02  2:18 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-31 17:13 [PATCH net 00/16] net: first round to use dev_net_rcu() Eric Dumazet
2025-01-31 17:13 ` [PATCH net 01/16] net: add dev_net_rcu() helper Eric Dumazet
2025-01-31 18:29   ` Kuniyuki Iwashima
2025-01-31 17:13 ` [PATCH net 02/16] ipv4: add RCU protection to ip4_dst_hoplimit() Eric Dumazet
2025-01-31 18:34   ` Kuniyuki Iwashima
2025-01-31 17:13 ` [PATCH net 03/16] ipv4: use RCU protection in ip_dst_mtu_maybe_forward() Eric Dumazet
2025-01-31 18:47   ` Kuniyuki Iwashima
2025-01-31 17:13 ` [PATCH net 04/16] ipv4: use RCU protection in ipv4_default_advmss() Eric Dumazet
2025-01-31 18:51   ` Kuniyuki Iwashima
2025-01-31 17:13 ` [PATCH net 05/16] ipv4: use RCU protection in rt_is_expired() Eric Dumazet
2025-01-31 19:00   ` Kuniyuki Iwashima
2025-01-31 17:13 ` [PATCH net 06/16] tcp: convert to dev_net_rcu() Eric Dumazet
2025-01-31 19:03   ` Kuniyuki Iwashima
2025-01-31 17:13 ` [PATCH net 07/16] net: gro: convert four dev_net() calls Eric Dumazet
2025-01-31 19:05   ` Kuniyuki Iwashima
2025-01-31 17:13 ` [PATCH net 08/16] udp: convert to dev_net_rcu() Eric Dumazet
2025-01-31 19:10   ` Kuniyuki Iwashima
2025-02-03  9:33     ` Eric Dumazet
2025-01-31 17:13 ` [PATCH net 09/16] ipv4: icmp: " Eric Dumazet
2025-01-31 19:12   ` Kuniyuki Iwashima
2025-01-31 17:13 ` [PATCH net 10/16] ipv6: " Eric Dumazet
2025-01-31 19:15   ` Kuniyuki Iwashima
2025-01-31 17:13 ` [PATCH net 11/16] ipv6: input: " Eric Dumazet
2025-01-31 19:21   ` Kuniyuki Iwashima
2025-01-31 17:13 ` [PATCH net 12/16] ipv6: output: " Eric Dumazet
2025-01-31 19:26   ` Kuniyuki Iwashima
2025-01-31 17:13 ` [PATCH net 13/16] ipv6: use RCU protection in ip6_default_advmss() Eric Dumazet
2025-01-31 19:35   ` Kuniyuki Iwashima
2025-01-31 17:13 ` [PATCH net 14/16] net: filter: convert to dev_net_rcu() Eric Dumazet
2025-01-31 19:37   ` Kuniyuki Iwashima
2025-01-31 17:13 ` [PATCH net 15/16] flow_dissector: use rcu protection to fetch dev_net() Eric Dumazet
2025-01-31 19:46   ` Kuniyuki Iwashima
2025-02-03 10:09     ` Eric Dumazet
2025-02-02  2:18 ` Jakub Kicinski [this message]
2025-02-03 10:12   ` [PATCH net 00/16] net: first round to use dev_net_rcu() Eric Dumazet

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=20250201181801.4427248a@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=horms@kernel.org \
    --cc=kuniyu@amazon.com \
    --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).