summaryrefslogtreecommitdiff
path: root/COPYING
diff options
context:
space:
mode:
authorAlexandre Bounine <alexandre.bounine@idt.com>2016-09-19 21:44:47 (GMT)
committerLinus Torvalds <torvalds@linux-foundation.org>2016-09-19 22:36:17 (GMT)
commitb92ae139c308c5223521ed6ec022148b81312809 (patch)
treeca05935b1c708bc8c982633781d46aed1b0070df /COPYING
parent63b52c4936a2e679639c38ef51a50aa8ca1c5c07 (diff)
downloadlinux-b92ae139c308c5223521ed6ec022148b81312809.tar.xz
rapidio/rio_cm: avoid GFP_KERNEL in atomic context
As reported by Alexey Khoroshilov (https://lkml.org/lkml/2016/9/9/737): riocm_send_close() is called from rio_cm_shutdown() under spin_lock_bh(idr_lock), but riocm_send_close() uses a GFP_KERNEL allocation. Fix by taking riocm_send_close() outside of spinlock protected code. [akpm@linux-foundation.org: remove unneeded `if (!list_empty())'] Link: http://lkml.kernel.org/r/20160915175402.10122-1-alexandre.bounine@idt.com Signed-off-by: Alexandre Bounine <alexandre.bounine@idt.com> Reported-by: Alexey Khoroshilov <khoroshilov@ispras.ru> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'COPYING')
0 files changed, 0 insertions, 0 deletions