From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Refcounting problem in rfcomm
Date: Mon, 31 Jul 2006 20:13:57 +0200 [thread overview]
Message-ID: <1154369637.4982.8.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0607311627330.31025@redbean.intranet.gw-instruments.de>
Hi Peter,
> while trying to implement a server tty which can be used without a user
> space daemon I came across a reference counting problem. Function
> rfcomm_accept_connection()
> calls __module_get(nsock->ops->owner) but there is no corresponding
> module_put(). I think for user space sockets this won't be a problem.
> However, if the owner of the socket is the rfcomm module itself the
> reference count gets wrong.
>
> A work around for this may be to decrement the reference count just before
> releasing the socket used for listening.
the RFCOMM module reference counting is not funny and you can mess it up
on so many level. So be careful with it. I haven't looked at it, but
from past experience I know that you can easily break things. So please
give us some more details or code to show the problem.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-07-31 18:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 14:44 [Bluez-devel] Refcounting problem in rfcomm Peter Wippich
2006-07-31 18:13 ` Marcel Holtmann [this message]
2006-07-31 16:33 ` Peter Wippich
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=1154369637.4982.8.camel@aeonflux.holtmann.net \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/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