From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, chuck.lever@oracle.com,
linux-nfs@vger.kernel.org, netdev@vger.kernel.org,
edumazet@google.com
Subject: Re: [PATCH net-next 0/3] SUNRPC: add some netns refcount trackers
Date: Fri, 28 Jan 2022 15:10:17 +0000 [thread overview]
Message-ID: <164338261720.2420.9086184599946096191.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220127200937.2157402-1-eric.dumazet@gmail.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 27 Jan 2022 12:09:34 -0800 you wrote:
> From: Eric Dumazet <edumazet@google.com>
>
> Effort started in linux-5.17
>
> Our goal is to replace get_net()/put_net() pairs with
> get_net_track()/put_net_track() to get instant notifications
> of imbalance bugs in the future.
>
> [...]
Here is the summary with links:
- [net-next,1/3] SUNRPC: add netns refcount tracker to struct svc_xprt
https://git.kernel.org/netdev/net-next/c/6cdef8a6ee74
- [net-next,2/3] SUNRPC: add netns refcount tracker to struct gss_auth
https://git.kernel.org/netdev/net-next/c/9b1831e56c7f
- [net-next,3/3] SUNRPC: add netns refcount tracker to struct rpc_xprt
https://git.kernel.org/netdev/net-next/c/b9a0d6d143ec
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-01-28 15:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 20:09 [PATCH net-next 0/3] SUNRPC: add some netns refcount trackers Eric Dumazet
2022-01-27 20:09 ` [PATCH net-next 1/3] SUNRPC: add netns refcount tracker to struct svc_xprt Eric Dumazet
2022-01-27 20:25 ` Chuck Lever III
2022-01-27 20:09 ` [PATCH net-next 2/3] SUNRPC: add netns refcount tracker to struct gss_auth Eric Dumazet
2022-01-27 20:09 ` [PATCH net-next 3/3] SUNRPC: add netns refcount tracker to struct rpc_xprt Eric Dumazet
2022-01-28 15:10 ` 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=164338261720.2420.9086184599946096191.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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.