From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Marcel Holtmann <marcel@holtmann.org>,
Max Krasnyansky <maxk@qualcomm.com>,
BlueZ mailing list <bluez-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Bluez-devel] Re: [BUG] BlueTooth socket busted in 2.6.0-test5
Date: Fri, 12 Sep 2003 14:34:15 -0700 [thread overview]
Message-ID: <20030912213415.GA24895@bougret.hpl.hp.com> (raw)
In-Reply-To: <1063354754.23778.380.camel@hades.cambridge.redhat.com>
On Fri, Sep 12, 2003 at 09:19:15AM +0100, David Woodhouse wrote:
> On Fri, 2003-09-12 at 06:21 +0100, David Woodhouse wrote:
> > Er, if we're actually _running_ code from the bnep module, how can it
> > have a zero refcount? This bug is elsewhere, surely?
>
> Please confirm this fixes it...
>
> ===== net/bluetooth/bnep/sock.c 1.11 vs edited =====
> --- 1.11/net/bluetooth/bnep/sock.c Thu Jun 5 01:57:08 2003
> +++ edited/net/bluetooth/bnep/sock.c Fri Sep 12 09:16:17 2003
> @@ -186,7 +189,8 @@
>
> static struct net_proto_family bnep_sock_family_ops = {
> .family = PF_BLUETOOTH,
> - .create = bnep_sock_create
> + .create = bnep_sock_create,
> + .owner = THIS_MODULE
> };
>
> int __init bnep_sock_init(void)
>
>
> --
> dwmw2
Sorry for the slow answer, but yes, this fixes the problem
(and yes, I've removed my temporary hack).
Thanks a lot !
Jean
prev parent reply other threads:[~2003-09-12 21:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-10 22:58 [BUG] BlueTooth socket busted in 2.6.0-test5 Jean Tourrilhes
2003-09-10 23:39 ` [Bluez-devel] " Marcel Holtmann
2003-09-10 23:47 ` Jean Tourrilhes
2003-09-11 20:32 ` Jean Tourrilhes
2003-09-12 5:21 ` [Bluez-devel] " David Woodhouse
2003-09-12 8:19 ` David Woodhouse
2003-09-12 21:34 ` Jean Tourrilhes [this message]
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=20030912213415.GA24895@bougret.hpl.hp.com \
--to=jt@bougret.hpl.hp.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=dwmw2@infradead.org \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=maxk@qualcomm.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