From: Dan Carpenter <dan.carpenter@oracle.com>
To: Cong Wang <amwang@redhat.com>
Cc: netdev@vger.kernel.org
Subject: Re: bonding: sync netpoll code with bridge
Date: Thu, 26 Jul 2012 11:17:01 +0300 [thread overview]
Message-ID: <20120726081700.GN4403@mwanda> (raw)
In-Reply-To: <1343286905.12207.7.camel@cr0>
On Thu, Jul 26, 2012 at 03:15:05PM +0800, Cong Wang wrote:
> On Wed, 2012-07-25 at 16:47 +0300, Dan Carpenter wrote:
> > Hello Amerigo Wang,
> >
> > The patch 8a8efa22f51b: "bonding: sync netpoll code with bridge" from
> > Feb 17, 2011, leads to the following warning:
> > drivers/net/bonding/bond_main.c:1849 bond_enslave()
> > error: scheduling with locks held: 'read_lock:&bond->lock'
>
> Yeah, makes sense. Just wondering why I didn't catch it when I tested
> that patch. Anyway, could you try the following patch?
>
The warnings were static checker warnings, not something I tested.
regards,
dan carpenter
prev parent reply other threads:[~2012-07-26 8:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 13:47 bonding: sync netpoll code with bridge Dan Carpenter
2012-07-26 7:15 ` Cong Wang
2012-07-26 8:17 ` Dan Carpenter [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=20120726081700.GN4403@mwanda \
--to=dan.carpenter@oracle.com \
--cc=amwang@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).