From: Jiri Pirko <jpirko@redhat.com>
To: Ben Hutchings <bhutchings@solarflare.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: Tue, 10 Jan 2012 00:47:43 +0100 [thread overview]
Message-ID: <20120109234743.GA4896@minipsycho> (raw)
In-Reply-To: <1326136028.2725.0.camel@bwh-desktop>
Mon, Jan 09, 2012 at 08:07:08PM CET, bhutchings@solarflare.com wrote:
>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'?
That's him :) I mixed that up a bit. Sorry :(
Jirka
>
>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.
>
next prev parent reply other threads:[~2012-01-09 23:47 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
2012-01-09 20:47 ` David Miller
2012-01-09 23:47 ` Jiri Pirko [this message]
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=20120109234743.GA4896@minipsycho \
--to=jpirko@redhat.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.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).