From: Juergen Gross <jgross@suse.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH linux-2.6.18] xen: mark pvscsi frontend request consumed only after last read
Date: Mon, 02 Feb 2015 11:17:43 +0100 [thread overview]
Message-ID: <54CF4EC7.9050507@suse.com> (raw)
In-Reply-To: <54CF3ADC020000780005BBD7@mail.emea.novell.com>
On 02/02/2015 08:52 AM, Jan Beulich wrote:
>>>> On 30.01.15 at 14:51, <"jgross@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 private field (if it
> was a shared one, a barrier would have been needed between
> copying and updating that field).
Hmm, you are right. Interesting, I've always thought req_cons would be
used by the frontend, too.
Thanks for updating my protocol know-how. :-)
>
>> To avoid inconsistencies in the backend only work on a private copy
>> of the request. This will ensure a malicious guest not being able to
>> bypass consistency checks of the backend by modifying an active
>> request.
>
> Hence - also considering with my earlier reply - I don't view the change
> as necessary.
Agreed.
Juergen
prev parent reply other threads:[~2015-02-02 10:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-30 13:51 [PATCH linux-2.6.18] xen: mark pvscsi frontend request consumed only after last read Juergen Gross
2015-01-30 14:22 ` Jan Beulich
2015-01-30 14:32 ` Jan Beulich
[not found] ` <54CBA41E020000780005B5D7@suse.com>
2015-01-30 14:40 ` Juergen Gross
[not found] ` <54CBA1CA020000780005B5A0@suse.com>
2015-01-30 14:26 ` Juergen Gross
2015-02-02 7:52 ` Jan Beulich
2015-02-02 10:17 ` Juergen Gross [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54CF4EC7.9050507@suse.com \
--to=jgross@suse.com \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.