netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Stanislav Fomichev <sdf@fomichev.me>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
	pabeni@redhat.com, Saeed Mahameed <saeed@kernel.org>
Subject: Re: [PATCH net-next v2 00/11] net: Hold netdev instance lock during ndo operations
Date: Sat, 15 Feb 2025 07:55:43 -0800	[thread overview]
Message-ID: <20250215075543.4ca1cd58@kernel.org> (raw)
In-Reply-To: <20250214153440.1994910-1-sdf@fomichev.me>

On Fri, 14 Feb 2025 07:34:29 -0800 Stanislav Fomichev wrote:
> As the gradual purging of rtnl continues, start grabbing netdev
> instance lock in more places so we can get to the state where
> most paths are working without rtnl. Start with requiring the
> drivers that use shaper api (and later queue mgmt api) to work
> with both rtnl and netdev instance lock. Eventually we might
> attempt to drop rtnl. This mostly affects iavf, gve, bnxt and
> netdev sim (as the drivers that implement shaper/queue mgmt)
> so those drivers are converted in the process.
> 
> call_netdevice_notifiers locking is very inconsistent and might need
> a separate follow up. Some notified events are covered by the
> instance lock, some are not, which might complicate the driver
> expectations.

Appears to break the CI build:

net/core/dev.c:11392:12: error: ‘netdev_lock_cmp_fn’ defined but not used [-Werror=unused-function]
11392 | static int netdev_lock_cmp_fn(const struct lockdep_map *a,
      |            ^~~~~~~~~~~~~~~~~~
-- 
pw-bot: cr

      parent reply	other threads:[~2025-02-15 15:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-14 15:34 [PATCH net-next v2 00/11] net: Hold netdev instance lock during ndo operations Stanislav Fomichev
2025-02-14 15:34 ` [PATCH net-next v2 01/11] net: hold netdev instance lock during ndo_open/ndo_stop Stanislav Fomichev
2025-02-14 15:34 ` [PATCH net-next v2 02/11] net: hold netdev instance lock during ndo_setup_tc Stanislav Fomichev
2025-02-14 15:34 ` [PATCH net-next v2 03/11] net: hold netdev instance lock during queue operations Stanislav Fomichev
2025-02-14 15:34 ` [PATCH net-next v2 04/11] net: hold netdev instance lock during rtnetlink operations Stanislav Fomichev
2025-02-14 15:34 ` [PATCH net-next v2 05/11] net: hold netdev instance lock during ioctl operations Stanislav Fomichev
2025-02-14 15:34 ` [PATCH net-next v2 06/11] net: hold netdev instance lock during sysfs operations Stanislav Fomichev
2025-02-14 15:34 ` [PATCH net-next v2 07/11] net: hold netdev instance lock during ndo_bpf Stanislav Fomichev
2025-02-14 15:34 ` [PATCH net-next v2 08/11] net: ethtool: try to protect all callback with netdev instance lock Stanislav Fomichev
2025-02-14 15:34 ` [PATCH net-next v2 09/11] net: dummy: add dummy shaper API Stanislav Fomichev
2025-02-14 15:34 ` [PATCH net-next v2 10/11] docs: net: document new locking reality Stanislav Fomichev
2025-02-14 15:34 ` [PATCH net-next v2 11/11] eth: bnxt: remove most dependencies on RTNL Stanislav Fomichev
2025-02-15 15:55 ` Jakub Kicinski [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=20250215075543.4ca1cd58@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=saeed@kernel.org \
    --cc=sdf@fomichev.me \
    /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).