From: David Vrabel <david.vrabel@citrix.com>
To: xen-devel@lists.xen.org
Cc: Keir Fraser <keir@xen.org>,
David Vrabel <david.vrabel@citrix.com>,
Jan Beulich <jbeulich@suse.com>
Subject: [PATCHv4 0/2] Xen: FIFO-based event channel ABI fixes
Date: Tue, 12 Nov 2013 11:38:46 +0000 [thread overview]
Message-ID: <1384256328-20223-1-git-send-email-david.vrabel@citrix.com> (raw)
This series address two design flaws in the FIFO-based event channel ABI.
1. Fix a potential DoS caused by an unbounded loop when setting LINK.
2. Fix queue corruption that may occurs when events are moved between
queues.
An updated design document is available from:
http://xenbits.xen.org/people/dvrabel/event-channels-H.pdf
- Add the BUSY bit to indicate that the guest must not clear MASKED.
v9 of the Linux patches have been posted already.
Changes in v4:
- const struct domain *
- Clear BUSY with existing cmpxchg() where possible.
- Fix BUSY bit debug output.
Changes in v3:
- Use a new BUSY bit to block guests from clearing UNMASKED, this is
lower overhead than the previous solution (which required a
hypercall).
- Fix another problem with moving events between queues.
- Add evtchn->last_vpcu_id and evtchn->last_priority instead of
evtchn->q. This keeps the structure at 32 bytes long.
Changes in v2:
- Add MAINTAINERS patch
- Remove some unnecessary temporary pending state clears
- Add fix for DoS
next reply other threads:[~2013-11-12 11:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 11:38 David Vrabel [this message]
2013-11-12 11:38 ` [PATCH 1/2] evtchn/fifo: don't spin indefinitely when setting LINK David Vrabel
2013-11-20 15:19 ` David Vrabel
2013-11-22 12:08 ` Jan Beulich
2013-11-12 11:38 ` [PATCH 2/2] evtchn/fifo: don't corrupt queues if an old tail moves queues David Vrabel
2013-11-15 13:15 ` David Vrabel
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=1384256328-20223-1-git-send-email-david.vrabel@citrix.com \
--to=david.vrabel@citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--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).