From: Marcel Holtmann <marcel@holtmann.org>
To: Tetsuo Shiraishi <tetsu@s-direct.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] rfcomm bind : Address already in use
Date: Mon, 12 Jul 2004 20:26:10 +0200 [thread overview]
Message-ID: <1089656770.4644.69.camel@pegasus> (raw)
In-Reply-To: <4.3.2-J.20040713015123.0463e378@emi.s-direct.com>
Hi Tetsuo,
> >you should have mentioned that, because dund creates a /dev/rfcommX
> >device node for starting PPP. Maybe there is a leftover, which leaves
> >the DLC open and so the session can't be terminated. Maybe a running
> >pppd holds the socket descriptor open.
> >
> >But I won't have time to look into that in detail. If you provide me a
> >patch for dund or for the kernel RFCOMM part, I will review it.
> >
>
> I tried to make patch for this.
sorry to say that, but that is not the solution. Implementing some kind
of garbage collection is not ok. This is the Linux kernel, if you think
that this is a bug, find it and fix it. And don't work around it.
Btw you forgot the locking while iteration along the socket list.
Regards
Marcel
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-07-12 18:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-09 17:21 [Bluez-devel] rfcomm bind : Address already in use Tetsuo Shiraishi
2004-07-09 18:13 ` Marcel Holtmann
2004-07-10 14:11 ` Tetsuo Shiraishi
2004-07-10 17:41 ` Marcel Holtmann
2004-07-12 17:16 ` Tetsuo Shiraishi
2004-07-12 18:26 ` Marcel Holtmann [this message]
2004-07-14 9:12 ` Tetsuo Shiraishi
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=1089656770.4644.69.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=tetsu@s-direct.com \
/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