Messages in this thread | | | Date | Mon, 07 Jul 2003 10:56:48 -0700 | From | Max Krasnyansky <> | Subject | Re: [Bluez-devel] Re: rfcomm oops in 2.5.74 |
| |
At 09:04 PM 7/3/2003, Dagfinn Ilmari Mannsåker wrote: >ilmari@ilmari.org (Dagfinn Ilmari MannsÃ¥ker) writes: > >> 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(). > >It turns out that net/bluetooth/rfcomm/sock.c (and >net/bluetooth/hci_sock.c) had been left out when net_proto_family gained >an owner field, here's a patch that fixes them both. Now I can transfer >pictures from my phone over OBEX Object Push again :) HCI socket doesn't need an owner field. But RFCOMM does I'll fix that.
Thanks for the patch Max
- 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/
| |