bluetooth: rfcomm_init bug fix
commitaf0d3b103bcfa877343ee338de12002cd50c9ee5
authorDave Young <hidave.darkstar@gmail.com>
Mon, 3 Aug 2009 04:26:16 +0000 (3 04:26 +0000)
committerDavid S. Miller <davem@davemloft.net>
Mon, 3 Aug 2009 20:24:39 +0000 (3 13:24 -0700)
treea06b348fae8d295b17e7620d00df6701f678d449
parenteb4ad826419ab5b1260bc1625249114767d36bea
bluetooth: rfcomm_init bug fix

rfcomm tty may be used before rfcomm_tty_driver initilized,
The problem is that now socket layer init before tty layer, if userspace
program do socket callback right here then oops will happen.

reporting in:
http://marc.info/?l=linux-bluetooth&m=124404919324542&w=2

make 3 changes:
1. remove #ifdef in rfcomm/core.c,
make it blank function when rfcomm tty not selected in rfcomm.h

2. tune the rfcomm_init error patch to ensure
tty driver initilized before rfcomm socket usage.

3. remove __exit for rfcomm_cleanup_sockets
because above change need call it in a __init function.

Reported-by: Oliver Hartkopp <oliver@hartkopp.net>
Tested-by: Oliver Hartkopp <oliver@hartkopp.net>
Signed-off-by: Dave Young <hidave.darkstar@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
include/net/bluetooth/rfcomm.h
net/bluetooth/rfcomm/core.c
net/bluetooth/rfcomm/sock.c