netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, pabeni@redhat.com, davem@davemloft.net,
	edumazet@google.com
Subject: Re: [patch net-next v2 0/3] devlink: don't take instance lock for nested handle put
Date: Wed, 11 Oct 2023 08:10:30 +0200	[thread overview]
Message-ID: <ZSY8Vg0ztfMN93uV@nanopsycho> (raw)
In-Reply-To: <20231010121015.5d9bb45d@kernel.org>

Tue, Oct 10, 2023 at 09:10:15PM CEST, kuba@kernel.org wrote:
>On Tue, 10 Oct 2023 11:13:20 +0200 Jiri Pirko wrote:
>> From: Jiri Pirko <jiri@nvidia.com>
>> 
>> Lockdep reports following issue:
>
>Weren't you complaining about people posting stuff before discussion
>is over in the past? :)

Sure, but it isn't? I believe that this fix is needed regardless of the
A->B objects lifetime. If I'm missing something, sorry about that.

      reply	other threads:[~2023-10-11  6:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-10  9:13 [patch net-next v2 0/3] devlink: don't take instance lock for nested handle put Jiri Pirko
2023-10-10  9:13 ` [patch net-next v2 1/3] net: treat possible_net_t net pointer as an RCU one and add read_pnet_rcu() Jiri Pirko
2023-10-10  9:13 ` [patch net-next v2 2/3] devlink: call peernet2id_alloc() with net pointer under RCU read lock Jiri Pirko
2023-10-10  9:13 ` [patch net-next v2 3/3] devlink: don't take instance lock for nested handle put Jiri Pirko
2023-10-10 19:10 ` [patch net-next v2 0/3] " Jakub Kicinski
2023-10-11  6:10   ` Jiri Pirko [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=ZSY8Vg0ztfMN93uV@nanopsycho \
    --to=jiri@resnulli.us \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --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).