+30
−8
Loading
In the previous fix: adc2942a nvmf: nvmf_ctrlr_get_log_page use iovs to store the log page a data corruption bug in the log page code was fixed. Previously, it used req->data, which may be too short a buffer in the case that the buffer is split across more than one IOV. req->data is never safe to use in this situation. The code was changed to use the provided iovs instead of req->data. However, the identify command handling was still vulnerable to this problem, and has been seen in real life at least with a CentOS guest VM. The fix is basically the same: use the IOV utility functions to write out the response instead of directly trying to use req->data. Signed-off-by:John Levon <john.levon@nutanix.com> Change-Id: I00445895af20e43be73189629576eee0667f86dd Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/16121 Reviewed-by:
Thanos Makatos <thanos.makatos@nutanix.com> Reviewed-by:
Jim Harris <james.r.harris@intel.com> Reviewed-by:
Shuhei Matsumoto <smatsumoto@nvidia.com> Tested-by:
SPDK CI Jenkins <sys_sgci@intel.com>