diff options
author | 2018-01-26 23:57:01 +0800 | |
---|---|---|
committer | 2018-02-07 09:48:56 +0100 | |
commit | 1ebbf046273e50cf3cbf2ec13d520dc74ab454d4 (patch) | |
tree | aec737a39b0b5515a29dd5563ea99ad6a2aadce8 /net/bluetooth/hci_request.c | |
parent | Bluetooth: hci_ath: Replace mdelay with msleep in ath_wakeup_ar3k (diff) | |
download | wireguard-linux-1ebbf046273e50cf3cbf2ec13d520dc74ab454d4.tar.xz wireguard-linux-1ebbf046273e50cf3cbf2ec13d520dc74ab454d4.zip |
Bluetooth: btmrvl_main: Replace GFP_ATOMIC with GFP_KERNEL in btmrvl_send_sync_cmd
After checking all possible call chains to btmrvl_send_sync_cmd(),
my tool finds that this function is never called in atomic context,
namely never in an interrupt handler or holding a spinlock.
And it calls wait_event_interruptible_timeout() after bt_skb_alloc(),
so it indicates that btmrvl_send_sync_cmd()
can call function which can sleep.
Thus GFP_ATOMIC is not necessary, and it can be replaced with GFP_KERNEL.
This is found by a static analysis tool named DCNS written by myself.
Signed-off-by: Jia-Ju Bai <baijiaju1990@gmail.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Diffstat (limited to 'net/bluetooth/hci_request.c')
0 files changed, 0 insertions, 0 deletions