Re: [Bluez-devel] rfcomm oops in 2.5.74

Aurelien Minet (a.minet@prim-time.fr)
Fri, 04 Jul 2003 09:39:39 +0200


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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/