From: David Miller <davem@davemloft.net>
To: khlebnikov@openvz.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
dmitry.tarnyagin@lockless.no
Subject: Re: [PATCH] drivers/net: caif: fix wrong rtnl_is_locked() usage
Date: Tue, 09 Jul 2013 12:56:32 -0700 (PDT) [thread overview]
Message-ID: <20130709.125632.1573031651619706332.davem@davemloft.net> (raw)
In-Reply-To: <20130708072304.20622.60798.stgit@zurg>
From: Konstantin Khlebnikov <khlebnikov@openvz.org>
Date: Mon, 08 Jul 2013 11:23:04 +0400
> rtnl_is_locked() doesn't check who holds this lock, it just tells that it's
> locked right now. if caif::ldisc_close really can be called under rtrnl_lock
> then it should release net device in other context because there is no way
> to grab rtnl_lock without deadlock.
>
> This patch adds work which releases these devices. Also this patch fixes calling
> dev_close/unregister_netdevice without rtnl_lock from caif_ser_exit().
>
> Signed-off-by: Konstantin Khlebnikov <khlebnikov@openvz.org>
Applied.
prev parent reply other threads:[~2013-07-09 19:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 7:23 [PATCH] drivers/net: caif: fix wrong rtnl_is_locked() usage Konstantin Khlebnikov
2013-07-09 19:56 ` David Miller [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=20130709.125632.1573031651619706332.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dmitry.tarnyagin@lockless.no \
--cc=khlebnikov@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--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).