From: Jukka Rissanen <jukka.rissanen@linux.intel.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH v5 4/5] Bluetooth: 6LoWPAN: Count module usage
Date: Mon, 2 Jun 2014 18:00:26 +0300 [thread overview]
Message-ID: <1401721227-28439-5-git-send-email-jukka.rissanen@linux.intel.com> (raw)
In-Reply-To: <1401721227-28439-1-git-send-email-jukka.rissanen@linux.intel.com>
Count how many 6LoWPAN connections there exists so that we
do not unload the module if there are still connections alive.
Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
---
net/bluetooth/6lowpan.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/net/bluetooth/6lowpan.c b/net/bluetooth/6lowpan.c
index debf003..90c64da 100644
--- a/net/bluetooth/6lowpan.c
+++ b/net/bluetooth/6lowpan.c
@@ -101,6 +101,8 @@ static inline bool peer_del(struct lowpan_dev *dev, struct lowpan_peer *peer)
{
list_del(&peer->list);
+ module_put(THIS_MODULE);
+
if (atomic_dec_and_test(&dev->peer_count)) {
BT_DBG("last peer");
return true;
@@ -744,6 +746,9 @@ static inline void chan_ready_cb(struct l2cap_chan *chan)
}
}
+ if (!try_module_get(THIS_MODULE))
+ return;
+
add_peer_chan(chan, dev);
ifup(dev->netdev);
}
--
1.8.3.1
next prev parent reply other threads:[~2014-06-02 15:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 15:00 [PATCH v5 0/5] Bluetooth LE 6LoWPAN using CoC Jukka Rissanen
2014-06-02 15:00 ` [PATCH v5 1/5] Bluetooth: Refactor l2cap_sock_sendmsg() to copy user buffer Jukka Rissanen
2014-06-03 3:49 ` Marcel Holtmann
2014-06-02 15:00 ` [PATCH v5 2/5] Bluetooth: 6LoWPAN: Use connected oriented channel instead of fixed one Jukka Rissanen
2014-06-03 3:55 ` Marcel Holtmann
2014-06-02 15:00 ` [PATCH v5 3/5] Bluetooth: 6LoWPAN: Create a kernel module Jukka Rissanen
2014-06-03 3:57 ` Marcel Holtmann
2014-06-02 15:00 ` Jukka Rissanen [this message]
2014-06-02 15:00 ` [PATCH v5 5/5] Bluetooth: 6LoWPAN: Remove network devices when unloading Jukka Rissanen
2014-06-03 4:00 ` Marcel Holtmann
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=1401721227-28439-5-git-send-email-jukka.rissanen@linux.intel.com \
--to=jukka.rissanen@linux.intel.com \
--cc=linux-bluetooth@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).