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: Thu, 03 Jul 2003 17:02:36 +0200 [thread overview]
Message-ID: <3F04458C.4070502@prim-time.fr> (raw)
In-Reply-To: <d8jznjvzr07.fsf@wirth.ping.uio.no>
Hi Dagfinn
> Calling socket(PF_BLUETOOTH, SOCK_RAW, BTPROTO_RFCOMM) on 2.5.74
> segfaults and gives the below oops. module.h:297 is
> BUG_ON(module_refcount(module) == 0) in __module_get(), which is called
> from rfcomm_sock_alloc() via sk_set_owner().
I don't know for 2.5.xx but for 2.4.xx in order to use RFCOMM protocol
you must use a SOCK_STREAM and not SOCK_RAW socket type.
(SOCK_RAW is for HCI , SOCK_SEQPACKET & SOCK_DGRAM for L2cap)
I think it must return an error instead of making a segfault, in this
way it is a bug.
Regards
Aurelien
next prev parent reply other threads:[~2003-07-03 14:50 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 ` Aurelien Minet [this message]
2003-07-03 15:54 ` [Bluez-devel] " Dagfinn Ilmari Mannsåker
2003-07-04 7:39 ` Aurelien Minet
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=3F04458C.4070502@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).