From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@suse.com>, xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] io/ring.h: drop unused and broken *_RING_ATTACH() macros
Date: Tue, 11 Jun 2013 11:09:50 +0100 [thread overview]
Message-ID: <CDDCB5FE.29203%keir.xen@gmail.com> (raw)
In-Reply-To: <51B7004002000078000DCFFF@nat28.tlf.novell.com>
On 11/06/2013 09:47, "Jan Beulich" <JBeulich@suse.com> wrote:
> Initializing r*_prod_pvt and r*_cons from independent shared ring
> fields is broken, as other macros in this header rely on them being
> coupled. Furthermore using the backend variant would also imply a
> security vulnerability.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
Acked-by: Keir Fraser <keir@xen.org>
> --- a/xen/include/public/io/ring.h
> +++ b/xen/include/public/io/ring.h
> @@ -174,21 +174,6 @@ typedef struct __name##_back_ring __name
> (_r)->sring = (_s); \
> } while (0)
>
> -/* Initialize to existing shared indexes -- for recovery */
> -#define FRONT_RING_ATTACH(_r, _s, __size) do { \
> - (_r)->sring = (_s); \
> - (_r)->req_prod_pvt = (_s)->req_prod; \
> - (_r)->rsp_cons = (_s)->rsp_prod; \
> - (_r)->nr_ents = __RING_SIZE(_s, __size); \
> -} while (0)
> -
> -#define BACK_RING_ATTACH(_r, _s, __size) do { \
> - (_r)->sring = (_s); \
> - (_r)->rsp_prod_pvt = (_s)->rsp_prod; \
> - (_r)->req_cons = (_s)->req_prod; \
> - (_r)->nr_ents = __RING_SIZE(_s, __size); \
> -} while (0)
> -
> /* How big is this ring? */
> #define RING_SIZE(_r) \
> ((_r)->nr_ents)
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
prev parent reply other threads:[~2013-06-11 10:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 8:47 [PATCH] io/ring.h: drop unused and broken *_RING_ATTACH() macros Jan Beulich
2013-06-11 10:09 ` Keir Fraser [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=CDDCB5FE.29203%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).