Paolo Bonzini 75f19f8c30 megasas: do not call pci_dma_unmap after having freed the frame once
Commit 8cc4678 ("megasas: remove useless check for cmd->frame", 2016-07-17) was
wrong because I trusted Coverity too much.  It turns out that there _is_ a
path through which cmd->frame can become NULL.  After megasas_handle_frame's
switch (md->frame->header.frame_cmd), megasas_init_firmware can be called.
From there, megasas_reset_frames will call megasas_unmap_frame which resets
cmd->frame = NULL.

However, there is another bug to fix in there, because megasas_unmap_frame
is called again after setting the command status.  In this case QEMU should
not do anything, instead it calls pci_dma_unmap again.  Harmless, but
better fix it.

Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2016-11-28 15:11:17 +01:00
..
2016-10-04 13:28:07 +01:00
2016-10-24 15:46:10 +02:00
2016-06-17 16:33:48 +10:00
2016-10-31 12:35:39 +00:00
2016-10-28 15:51:27 +01:00
2016-11-21 11:09:58 +00:00
2016-05-18 15:04:27 +03:00
2016-10-24 15:27:20 +02:00
2016-07-29 00:07:09 +03:00
2016-01-29 15:07:25 +00:00
2016-09-22 18:13:08 +01:00
2016-09-15 15:32:22 +03:00
2016-09-29 11:43:22 +08:00
2016-10-28 18:17:24 +03:00
2016-09-15 15:32:22 +03:00
2016-10-24 15:27:20 +02:00
2016-10-04 13:28:07 +01:00