On 02/02/2015 08:52 AM, Jan Beulich wrote:
On 30.01.15 at 14:51, jgr...@suse.com.non-mime.internet wrote:
A request in the ring buffer mustn't be read after it has been marked
as consumed. Otherwise it might already have been reused by the
frontend without violating the ring protocol.
This is
On 30.01.15 at 14:51, jgr...@suse.com.non-mime.internet wrote:
A request in the ring buffer mustn't be read after it has been marked
as consumed. Otherwise it might already have been reused by the
frontend without violating the ring protocol.
This is irrelevant, as the -req_cons is a backend
On 30.01.15 at 14:51, jgr...@suse.com.non-mime.internet wrote:
A request in the ring buffer mustn't be read after it has been marked
as consumed. Otherwise it might already have been reused by the
frontend without violating the ring protocol.
To avoid inconsistencies in the backend only
A request in the ring buffer mustn't be read after it has been marked
as consumed. Otherwise it might already have been reused by the
frontend without violating the ring protocol.
To avoid inconsistencies in the backend only work on a private copy
of the request. This will ensure a malicious
