summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/stackcollapse.py
diff options
context:
space:
mode:
authorGreg KH <gregkh@linuxfoundation.org>2019-10-01 18:56:11 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2019-10-29 09:20:09 +0100
commit27414f90ff6e1d7f6657e4a820b04a7b2d760272 (patch)
treea0fa38b9a69f4a4332d4b832b566130586ac30f2 /tools/perf/scripts/python/stackcollapse.py
parent054441182b51beca00f0c639b0119a1995143772 (diff)
RDMA/cxgb4: Do not dma memory off of the stack
commit 3840c5b78803b2b6cc1ff820100a74a092c40cbb upstream. Nicolas pointed out that the cxgb4 driver is doing dma off of the stack, which is generally considered a very bad thing. On some architectures it could be a security problem, but odds are none of them actually run this driver, so it's just a "normal" bug. Resolve this by allocating the memory for a message off of the heap instead of the stack. kmalloc() always will give us a proper memory location that DMA will work correctly from. Link: https://lore.kernel.org/r/20191001165611.GA3542072@kroah.com Reported-by: Nicolas Waisman <nico@semmle.com> Tested-by: Potnuri Bharat Teja <bharat@chelsio.com> Signed-off-by: Jason Gunthorpe <jgg@mellanox.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions