netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Hutchings <bhutchings@solarflare.com>
To: Jiri Pirko <jpirko@redhat.com>
Cc: <netdev@vger.kernel.org>, <davem@davemloft.net>,
	<eric.dumazet@gmail.com>
Subject: Re: [patch net-next v2 2/2] net: introduce netif_addr_lock_nested() and call if when appropriate
Date: Mon, 9 Jan 2012 19:07:08 +0000	[thread overview]
Message-ID: <1326136028.2725.0.camel@bwh-desktop> (raw)
In-Reply-To: <20120109163654.GC2114@minipsycho.brq.redhat.com>

On Mon, 2012-01-09 at 17:36 +0100, Jiri Pirko wrote:
> dev_uc_sync() and dev_mc_sync() are acquiring netif_addr_lock for
> destination device of synchronization. Since netif_addr_lock is already
> held at the time for source device, this triggers depmod deathlock
> warning.
[...]

I think you mean '...lockdep deadlock warning'?

Ben.

-- 
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.

  reply	other threads:[~2012-01-09 19:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-09 16:18 [patch net-next 1/2] net: correct lock name in dev_[uc/mc]_sync documentations Jiri Pirko
2012-01-09 16:18 ` [patch net-next 2/2] net: introduce netif_addr_lock_nested() and call if when appropriate Jiri Pirko
2012-01-09 16:36   ` [patch net-next v2 " Jiri Pirko
2012-01-09 19:07     ` Ben Hutchings [this message]
2012-01-09 20:47       ` David Miller
2012-01-09 23:47       ` Jiri Pirko
2012-01-09 20:47 ` [patch net-next 1/2] net: correct lock name in dev_[uc/mc]_sync documentations David Miller

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=1326136028.2725.0.camel@bwh-desktop \
    --to=bhutchings@solarflare.com \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=jpirko@redhat.com \
    --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 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).