Re: [Xen-devel] [PATCH v2 1/3] xen: fix quad word bufioreq handling

2016-11-28 Thread Stefano Stabellini
On Fri, 25 Nov 2016, Jan Beulich wrote: > 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 inf

Re: [Xen-devel] [PATCH v2 1/3] xen: fix quad word bufioreq handling

2016-11-25 Thread Paul Durrant
> -Original Message- > From: Jan Beulich [mailto:jbeul...@suse.com] > Sent: 25 November 2016 10:06 > To: qemu-de...@nongnu.org > Cc: Anthony Perard ; Paul Durrant > ; Stefano Stabellini ; xen- > devel > Subject: [PATCH v2 1/3] xen: fix quad word bufioreq handling > > We should not consume

[Xen-devel] [PATCH v2 1/3] xen: fix quad word bufioreq handling

2016-11-25 Thread Jan Beulich
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: yanghongk