| commit | ff3b8b8f864fa5721b196ca3dcc48853b0ee0275 | |
| author | Jan Beulich <JBeulich@suse.com> | |
| Fri, 25 Nov 2016 10:05:57 +0000 (25 03:05 -0700) | ||
| committer | Stefano Stabellini <sstabellini@kernel.org> | |
| Mon, 28 Nov 2016 19:25:23 +0000 (28 11:25 -0800) | ||
| tree | cb46e54d698a9bf3e3bcc2f6f7240464be5c5c39 | treesnapshot (tar.gz zip) |
| parent | 7875efb9f641ed0e79320bf258ee69cd0bf03716 | commitdiff |
xen: fix quad word bufioreq handling
We should not consume the second slot if it didn't get written yet.
Normal writers - i.e. Xen - would not update write_pointer between the
two writes, but the page may get fiddled with by the guest itself, and
we're better off avoiding to enter an infinite loop in that case.
Reported-by: yanghongke <yanghongke@huawei.com>
Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Paul Durrant <paul.durrant@citrix.com>
Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
Signed-off-by: Stefano Stabellini <sstabellini@kernel.org>
We should not consume the second slot if it didn't get written yet.
Normal writers - i.e. Xen - would not update write_pointer between the
two writes, but the page may get fiddled with by the guest itself, and
we're better off avoiding to enter an infinite loop in that case.
Reported-by: yanghongke <yanghongke@huawei.com>
Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Paul Durrant <paul.durrant@citrix.com>
Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
Signed-off-by: Stefano Stabellini <sstabellini@kernel.org>
| xen-hvm.c | diffblobblamehistory |