diff options
| author | Christophe JAILLET <[email protected]> | 2020-08-09 11:29:06 +0200 |
|---|---|---|
| committer | Kalle Valo <[email protected]> | 2020-08-18 15:52:11 +0300 |
| commit | d2ab7f00f4321370a8ee14e5630d4349fdacc42e (patch) | |
| tree | 6716643515b69f19297b673d14be0287c1ba814d /tools/perf/scripts/python | |
| parent | 2c762ee51008f14c642f50631a5485d33293ba40 (diff) | |
mwifiex: Do not use GFP_KERNEL in atomic context
A possible call chain is as follow:
mwifiex_sdio_interrupt (sdio.c)
--> mwifiex_main_process (main.c)
--> mwifiex_process_cmdresp (cmdevt.c)
--> mwifiex_process_sta_cmdresp (sta_cmdresp.c)
--> mwifiex_ret_802_11_scan (scan.c)
--> mwifiex_parse_single_response_buf (scan.c)
'mwifiex_sdio_interrupt()' is an interrupt function.
Also note that 'mwifiex_ret_802_11_scan()' already uses GFP_ATOMIC.
So use GFP_ATOMIC instead of GFP_KERNEL when memory is allocated in
'mwifiex_parse_single_response_buf()'.
Fixes: 7c6fa2a843c5 ("mwifiex: use cfg80211 dynamic scan table and cfg80211_get_bss API")
or
Fixes: 601216e12c65e ("mwifiex: process RX packets in SDIO IRQ thread directly")
Signed-off-by: Christophe JAILLET <[email protected]>
Signed-off-by: Kalle Valo <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions