All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	netdev@vger.kernel.org, eric.dumazet@gmail.com,
	syzkaller@googlegroups.com, jiri@nvidia.com
Subject: Re: [PATCH net-next] inet6: expand rcu_read_lock() scope in inet6_dump_addr()
Date: Thu, 29 Feb 2024 04:40:27 +0000	[thread overview]
Message-ID: <170918162703.21906.7688062355944676412.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240227222259.4081489-1-edumazet@google.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Tue, 27 Feb 2024 22:22:59 +0000 you wrote:
> I missed that inet6_dump_addr() is calling in6_dump_addrs()
> from two points.
> 
> First one under RTNL protection, and second one under rcu_read_lock().
> 
> Since we want to remove RTNL use from inet6_dump_addr() very soon,
> no longer assume in6_dump_addrs() is protected by RTNL (even
> if this is still the case).
> 
> [...]

Here is the summary with links:
  - [net-next] inet6: expand rcu_read_lock() scope in inet6_dump_addr()
    https://git.kernel.org/netdev/net-next/c/67ea41d19d2a

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-02-29  4:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-27 22:22 [PATCH net-next] inet6: expand rcu_read_lock() scope in inet6_dump_addr() Eric Dumazet
2024-02-28  7:39 ` Jiri Pirko
2024-02-29  4:40 ` patchwork-bot+netdevbpf [this message]

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=170918162703.21906.7688062355944676412.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=jiri@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=syzkaller@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.