linux-stable/net/bluetooth
Linus Torvalds 8926dd7e90 bluetooth: don't use bitmaps for random flag accesses
[ Upstream commit e1cff7002b ]

The bluetooth code uses our bitmap infrastructure for the two bits (!)
of connection setup flags, and in the process causes odd problems when
it converts between a bitmap and just the regular values of said bits.

It's completely pointless to do things like bitmap_to_arr32() to convert
a bitmap into a u32.  It shoudln't have been a bitmap in the first
place.  The reason to use bitmaps is if you have arbitrary number of
bits you want to manage (not two!), or if you rely on the atomicity
guarantees of the bitmap setting and clearing.

The code could use an "atomic_t" and use "atomic_or/andnot()" to set and
clear the bit values, but considering that it then copies the bitmaps
around with "bitmap_to_arr32()" and friends, there clearly cannot be a
lot of atomicity requirements.

So just use a regular integer.

In the process, this avoids the warnings about erroneous use of
bitmap_from_u64() which were triggered on 32-bit architectures when
conversion from a u64 would access two words (and, surprise, surprise,
only one word is needed - and indeed overkill - for a 2-bit bitmap).

That was always problematic, but the compiler seems to notice it and
warn about the invalid pattern only after commit 0a97953fd2 ("lib: add
bitmap_{from,to}_arr64") changed the exact implementation details of
'bitmap_from_u64()', as reported by Sudip Mukherjee and Stephen Rothwell.

Fixes: fe92ee6425 ("Bluetooth: hci_core: Rework hci_conn_params flags")
Link: https://lore.kernel.org/all/YpyJ9qTNHJzz0FHY@debian/
Link: https://lore.kernel.org/all/20220606080631.0c3014f2@canb.auug.org.au/
Link: https://lore.kernel.org/all/20220605162537.1604762-1-yury.norov@gmail.com/
Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
Reported-by: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Reviewed-by: Yury Norov <yury.norov@gmail.com>
Cc: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Cc: Marcel Holtmann <marcel@holtmann.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
2022-06-14 18:41:26 +02:00
..
bnep
cmtp
hidp
rfcomm
6lowpan.c
Kconfig
Makefile
a2mp.c
a2mp.h
af_bluetooth.c proc: remove PDE_DATA() completely 2022-01-22 08:33:37 +02:00
amp.c
amp.h
aosp.c
aosp.h
ecdh_helper.c
ecdh_helper.h
eir.c
eir.h Bluetooth: Fix skb allocation in mgmt_remote_name() & mgmt_device_connected() 2022-04-08 13:58:15 +02:00
hci_codec.c
hci_codec.h
hci_conn.c Bluetooth: hci_conn: Fix hci_connect_le_sync 2022-06-09 10:25:59 +02:00
hci_core.c bluetooth: don't use bitmaps for random flag accesses 2022-06-14 18:41:26 +02:00
hci_debugfs.c
hci_debugfs.h
hci_event.c Bluetooth: hci_conn: Fix hci_connect_le_sync 2022-06-09 10:25:59 +02:00
hci_request.c bluetooth: don't use bitmaps for random flag accesses 2022-06-14 18:41:26 +02:00
hci_request.h
hci_sock.c
hci_sync.c bluetooth: don't use bitmaps for random flag accesses 2022-06-14 18:41:26 +02:00
hci_sysfs.c
l2cap_core.c Bluetooth: use memset avoid memory leaks 2022-04-13 19:27:19 +02:00
l2cap_sock.c
leds.c
leds.h
lib.c
mgmt.c bluetooth: don't use bitmaps for random flag accesses 2022-06-14 18:41:26 +02:00
mgmt_config.c
mgmt_config.h
mgmt_util.c Bluetooth: assign len after null check 2022-02-24 21:05:21 +01:00
mgmt_util.h
msft.c
msft.h
sco.c Bluetooth: fix dangling sco_conn and use-after-free in sco_sock_timeout 2022-06-09 10:25:52 +02:00
selftest.c
selftest.h
smp.c
smp.h