+1
−0
Loading
The kernel vhost target enables notifying after processing each interrupt in a following manner. * unset NO_NOTIFY flag * mb() * check avail ring for slipped requests And we do the following after issuing each I/O. * update avail ring * check NO_NOTIFY If NO_NOTIFY check is reordered and read first, we might read old `true` value, and avail ring might be updated after the kernel has already done its check. This easily leads to deadlock. Change-Id: I6bb4490775dfed6fb2987e97c39b713054ae26ad Signed-off-by:Dariusz Stojaczyk <dariuszx.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/396499 Tested-by:
SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by:
Jim Harris <james.r.harris@intel.com> Reviewed-by:
Daniel Verkamp <daniel.verkamp@intel.com>