linux-toradex.git/net/bluetooth/rfcomm, branch v2.6.31.2

bluetooth: rfcomm_init bug fix

2009-08-03T20:24:39+00:00

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 
Tested-by: Oliver Hartkopp 
Signed-off-by: Dave Young 
Signed-off-by: David S. Miller

Bluetooth: Remove pointless endian conversion helpers

2009-06-08T12:50:01+00:00

The Bluetooth source uses some endian conversion helpers, that in the end
translate to kernel standard routines. So remove this obfuscation since it
is fully pointless.

Signed-off-by: Marcel Holtmann

Bluetooth: Fix removing of RFCOMM DLC timer with DEFER_SETUP

2009-04-19T16:56:45+00:00

There is a missing call to rfcomm_dlc_clear_timer in the case that
DEFER_SETUP is used and so the connection gets disconnected after the
timeout even if it was successfully accepted previously.

This patch adds a call to rfcomm_dlc_clear_timer to rfcomm_dlc_accept
which will get called when the user accepts the connection by calling
read() on the socket.

Signed-off-by: Johan Hedberg 
Signed-off-by: Marcel Holtmann

proc tty: remove struct tty_operations::read_proc

2009-04-01T15:59:10+00:00

struct tty_operations::proc_fops took it's place and there is one less
create_proc_read_entry() user now!

Signed-off-by: Alexey Dobriyan 
Cc: Alan Cox 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

Merge branch 'master' of /home/davem/src/GIT/linux-2.6/

2009-03-26T22:23:24+00:00

Conflicts:
	drivers/net/wimax/i2400m/usb-notif.c

Driver core: Fix device_move() vs. dpm list ordering, v2

2009-03-24T23:38:26+00:00

dpm_list currently relies on the fact that child devices will
be registered after their parents to get a correct suspend
order. Using device_move() however destroys this assumption, as
an already registered device may be moved under a newly registered
one.

This patch adds a new argument to device_move(), allowing callers
to specify how dpm_list should be adapted.

Signed-off-by: Cornelia Huck 
Acked-by: Alan Stern 
Signed-off-by: Greg Kroah-Hartman

Bluetooth: Fix RFCOMM usage of in-kernel L2CAP sockets

2009-02-27T05:14:48+00:00

The CID value of L2CAP sockets need to be set to zero. All userspace
applications do this via memset() on the sockaddr_l2 structure. The
RFCOMM implementation uses in-kernel L2CAP sockets and so it has to
make sure that l2_cid is set to zero.

Signed-off-by: Marcel Holtmann

Bluetooth: Change RFCOMM to use BT_CONNECT2 for BT_DEFER_SETUP

2009-02-27T05:14:47+00:00

When BT_DEFER_SETUP is enabled on a RFCOMM socket, then switch its
current state from BT_OPEN to BT_CONNECT2. This gives the Bluetooth
core a unified way to handle L2CAP and RFCOMM sockets. The BT_CONNECT2
state is designated for incoming connections.

Signed-off-by: Marcel Holtmann

Bluetooth: Use general bonding whenever possible

2009-02-27T05:14:40+00:00

When receiving incoming connection to specific services, always use
general bonding. This ensures that the link key gets stored and can be
used for further authentications.

Signed-off-by: Marcel Holtmann

Bluetooth: When encryption is dropped, do not send RFCOMM packets

2009-02-27T05:14:35+00:00

During a role change with pre-Bluetooth 2.1 devices, the remote side drops
the encryption of the RFCOMM connection. We allow a grace period for the
encryption to be re-established, before dropping the connection. During
this grace period, the RFCOMM_SEC_PENDING flag is set. Check this flag
before sending RFCOMM packets.

Signed-off-by: Jaikumar Ganesh 
Signed-off-by: Marcel Holtmann