From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, jiri@resnulli.us,
leon@kernel.org, mkubecek@suse.cz, andrew@lunn.ch,
f.fainelli@gmail.com
Subject: Re: [PATCH net-next v2 0/4] improve ethtool/rtnl vs devlink locking
Date: Mon, 01 Nov 2021 13:30:08 +0000 [thread overview]
Message-ID: <163577340840.3113.1602919922827934638.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211030171851.1822583-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Sat, 30 Oct 2021 10:18:47 -0700 you wrote:
> During ethtool netlink development we decided to move some of
> the commmands to devlink. Since we don't want drivers to implement
> both devlink and ethtool version of the commands ethtool ioctl
> falls back to calling devlink. Unfortunately devlink locks must
> be taken before rtnl_lock. This results in a questionable
> dev_hold() / rtnl_unlock() / devlink / rtnl_lock() / dev_put()
> pattern.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/4] ethtool: push the rtnl_lock into dev_ethtool()
https://git.kernel.org/netdev/net-next/c/f49deaa64af1
- [net-next,v2,2/4] ethtool: handle info/flash data copying outside rtnl_lock
https://git.kernel.org/netdev/net-next/c/095cfcfe13e5
- [net-next,v2,3/4] devlink: expose get/put functions
https://git.kernel.org/netdev/net-next/c/46db1b77cd4f
- [net-next,v2,4/4] ethtool: don't drop the rtnl_lock half way thru the ioctl
https://git.kernel.org/netdev/net-next/c/1af0a0948e28
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:[~2021-11-01 13:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-30 17:18 [PATCH net-next v2 0/4] improve ethtool/rtnl vs devlink locking Jakub Kicinski
2021-10-30 17:18 ` [PATCH net-next v2 1/4] ethtool: push the rtnl_lock into dev_ethtool() Jakub Kicinski
2021-10-31 6:19 ` Leon Romanovsky
2021-10-30 17:18 ` [PATCH net-next v2 2/4] ethtool: handle info/flash data copying outside rtnl_lock Jakub Kicinski
2021-10-31 6:24 ` Leon Romanovsky
2021-10-30 17:18 ` [PATCH net-next v2 3/4] devlink: expose get/put functions Jakub Kicinski
2021-10-31 6:29 ` Leon Romanovsky
2021-11-01 13:44 ` Jakub Kicinski
2021-11-01 18:11 ` Leon Romanovsky
2021-10-30 17:18 ` [PATCH net-next v2 4/4] ethtool: don't drop the rtnl_lock half way thru the ioctl Jakub Kicinski
2021-10-31 6:31 ` Leon Romanovsky
2021-11-01 13:30 ` 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=163577340840.3113.1602919922827934638.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=mkubecek@suse.cz \
--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.