diff options
| author | Sebastian Ott <sebott@linux.vnet.ibm.com> | 2016-04-15 09:41:35 +0200 |
|---|---|---|
| committer | Mister Oyster <oysterized@gmail.com> | 2017-07-04 12:11:07 +0200 |
| commit | 94bced6754a541230616836ce9f63e962bc8d4d2 (patch) | |
| tree | 0352ac80e8e8aecb67cadb06f2d86121aa9ba68b /drivers | |
| parent | f7dccfe9274bf6c463cd5bc6184543bd8e8efedc (diff) | |
s390/pci: fix use after free in dma_init
commit dba599091c191d209b1499511a524ad9657c0e5a upstream.
After a failure during registration of the dma_table (because of the
function being in error state) we free its memory but don't reset the
associated pointer to zero.
When we then receive a notification from firmware (about the function
being in error state) we'll try to walk and free the dma_table again.
Fix this by resetting the dma_table pointer. In addition to that make
sure that we free the iommu_bitmap when appropriate.
Signed-off-by: Sebastian Ott <sebott@linux.vnet.ibm.com>
Reviewed-by: Gerald Schaefer <gerald.schaefer@de.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: Sumit Semwal <sumit.semwal@linaro.org>
Signed-off-by: Jiri Slaby <jslaby@suse.cz>
Signed-off-by: Willy Tarreau <w@1wt.eu>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions