diff options
| author | Szymon Janc <szymon.janc@tieto.com> | 2012-06-08 11:33:33 +0200 |
|---|---|---|
| committer | Gustavo Padovan <gustavo.padovan@collabora.co.uk> | 2012-06-11 23:50:28 -0300 |
| commit | 8f321f853ea33330c7141977cd34804476e2e07e (patch) | |
| tree | 6b9a68b87086b13cac84d3bb300b666f133a0e6a /drivers/clocksource | |
| parent | 6eda541d12116b4772baa09d3e8d7b0389df4289 (diff) | |
| download | linux-stable-8f321f853ea33330c7141977cd34804476e2e07e.tar.gz linux-stable-8f321f853ea33330c7141977cd34804476e2e07e.tar.bz2 linux-stable-8f321f853ea33330c7141977cd34804476e2e07e.zip | |
Bluetooth: Fix using uninitialized option in RFCMode
If remote device sends bogus RFC option with invalid length,
undefined options values are used. Fix this by using defaults when
remote misbehaves.
This also fixes the following warning reported by gcc 4.7.0:
net/bluetooth/l2cap_core.c: In function 'l2cap_config_rsp':
net/bluetooth/l2cap_core.c:3302:13: warning: 'rfc.max_pdu_size' may be used uninitialized in this function [-Wmaybe-uninitialized]
net/bluetooth/l2cap_core.c:3266:24: note: 'rfc.max_pdu_size' was declared here
net/bluetooth/l2cap_core.c:3298:25: warning: 'rfc.monitor_timeout' may be used uninitialized in this function [-Wmaybe-uninitialized]
net/bluetooth/l2cap_core.c:3266:24: note: 'rfc.monitor_timeout' was declared here
net/bluetooth/l2cap_core.c:3297:25: warning: 'rfc.retrans_timeout' may be used uninitialized in this function [-Wmaybe-uninitialized]
net/bluetooth/l2cap_core.c:3266:24: note: 'rfc.retrans_timeout' was declared here
net/bluetooth/l2cap_core.c:3295:2: warning: 'rfc.mode' may be used uninitialized in this function [-Wmaybe-uninitialized]
net/bluetooth/l2cap_core.c:3266:24: note: 'rfc.mode' was declared here
Signed-off-by: Szymon Janc <szymon.janc@tieto.com>
Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
Diffstat (limited to 'drivers/clocksource')
0 files changed, 0 insertions, 0 deletions