diff options
| author | Jia-Ju Bai <baijiaju1990@163.com> | 2017-06-10 16:49:39 +0800 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2017-06-10 18:19:45 -0400 |
| commit | f146e872eb12ebbe92d8e583b2637e0741440db3 (patch) | |
| tree | 11df674fe1f70d91c86b2a63cfec66f8823ecfd1 /kernel/range.c | |
| parent | 5aa32f53ab93175442dffbd95a231d0798cab4d1 (diff) | |
| download | linux-f146e872eb12ebbe92d8e583b2637e0741440db3.tar.bz2 | |
net: caif: Fix a sleep-in-atomic bug in cfpkt_create_pfx
The kernel may sleep under a rcu read lock in cfpkt_create_pfx, and the
function call path is:
cfcnfg_linkup_rsp (acquire the lock by rcu_read_lock)
cfctrl_linkdown_req
cfpkt_create
cfpkt_create_pfx
alloc_skb(GFP_KERNEL) --> may sleep
cfserl_receive (acquire the lock by rcu_read_lock)
cfpkt_split
cfpkt_create_pfx
alloc_skb(GFP_KERNEL) --> may sleep
There is "in_interrupt" in cfpkt_create_pfx to decide use "GFP_KERNEL" or
"GFP_ATOMIC". In this situation, "GFP_KERNEL" is used because the function
is called under a rcu read lock, instead in interrupt.
To fix it, only "GFP_ATOMIC" is used in cfpkt_create_pfx.
Signed-off-by: Jia-Ju Bai <baijiaju1990@163.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'kernel/range.c')
0 files changed, 0 insertions, 0 deletions