From: Aurelien Minet <a.minet@prim-time.fr>
To: "Dagfinn Ilmari Mannsåker" <ilmari@ilmari.org>
Cc: bluez-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [Bluez-devel] rfcomm oops in 2.5.74
Date: Fri, 04 Jul 2003 09:39:39 +0200 [thread overview]
Message-ID: <3F052F3B.8090603@prim-time.fr> (raw)
In-Reply-To: <d8jptkrzjvh.fsf@wirth.ping.uio.no>
Hi Dagfinn
> I noticed it when rfcomm(1) segfaulted and caused the oops on startup,
> so I straced it. The strace output is:
>
> [linking stuff snipped]
> socket(0x1f /* PF_??? */, SOCK_RAW, 3 <unfinished ...>
> +++ killed by SIGSEGV +++
>
> According to <net/bluetooth/bluetooth.h> 0x1f is PF_BLUETOOTH and 3 is
> PTPROTO_RFCOMM. Looking at the source, rfcomm(1) uses SOCK_RAW for the
> RFCOMM control socket (for ioctls: RFCOMMGETDEVLIST, RFCOMMCREATEDEV,
> RFCOMMRELEASEDEV, RFCOMMGETDEVINFO), and SOCK_STREAM for the data
> sockets.
>
> What is the correct way of doing these ioctls on 2.5 if not against a
> SOCK_RAW socket?
Yes, the use of iotcl need SOCK_RAW socket. But I am not aware about
iotcl with RFCOMM (just whit HCI) and even less under 2.5 .
But I saw in 2.4 that it is for the TTY RFCOMM module, I think it should
only be used in this module.
If it is while your are using TTY over bluetooth, ask Marcel and Max on
Bluez List they can help you much more than me.
Sorry for the lack of help
Aurelien
next prev parent reply other threads:[~2003-07-04 7:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-03 13:20 rfcomm oops in 2.5.74 Dagfinn Ilmari Mannsåker
2003-07-03 15:02 ` [Bluez-devel] " Aurelien Minet
2003-07-03 15:54 ` Dagfinn Ilmari Mannsåker
2003-07-04 7:39 ` Aurelien Minet [this message]
2003-07-04 4:04 ` Dagfinn Ilmari Mannsåker
2003-07-07 17:56 ` [Bluez-devel] " Max Krasnyansky
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=3F052F3B.8090603@prim-time.fr \
--to=a.minet@prim-time.fr \
--cc=bluez-devel@lists.sourceforge.net \
--cc=ilmari@ilmari.org \
--cc=linux-kernel@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).