diff options
author | Takashi Iwai <tiwai@suse.de> | 2018-03-16 18:41:49 +0300 |
---|---|---|
committer | Kalle Valo <kvalo@codeaurora.org> | 2018-03-27 12:09:05 +0300 |
commit | b1c2d0f2507bf56d9f4dbd46dc4b99240fbd187c (patch) | |
tree | aedcc76006868738bc387d271b4ce19d65a00cf8 /tools/perf/scripts/python/export-to-sqlite.py | |
parent | 48eaee3f272a5bfe6986d07c51f6975d3c2f74d1 (diff) | |
download | linux-b1c2d0f2507bf56d9f4dbd46dc4b99240fbd187c.tar.xz |
brcmsmac: allocate ucode with GFP_KERNEL
The brcms_ucode_init_buf() duplicates the ucode chunks via kmemdup()
with GFP_ATOMIC as a precondition of wl->lock acquired. This caused
allocation failures sometimes as reported in the bugzilla below.
When looking at the the real usage, one can find that it's called
solely from brcms_request_fw(), and it's obviously outside the lock.
Hence we can use GFP_KERNEL there safely for avoiding such allocation
errors.
Bugzilla: http://bugzilla.suse.com/show_bug.cgi?id=1085174
Signed-off-by: Takashi Iwai <tiwai@suse.de>
Acked-by: Arend van Spriel <arend.vanspriel@broadcom.com>
Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions