xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Nathan Studer <nate.studer@dornerworks.com>
To: xen-devel@lists.xen.org
Cc: george.dunlap@eu.citrix.com, smartin@milliways.cl,
	Nathan Studer <nate.studer@dornerworks.com>,
	robert.vanvossen@dornerworks.com
Subject: [PATCH 0/2] Fix crashes with arinc653 cpupools
Date: Thu, 31 Oct 2013 16:47:51 -0400	[thread overview]
Message-ID: <1383252473-3067-1-git-send-email-nate.studer@dornerworks.com> (raw)

From: Nathan Studer <nate.studer@dornerworks.com>

The ARINC653 scheduler's vdata_alloc and vdata_free functions
contain a number of errors which cause the hypervisor
to crash when using the ARINC653 scheduler with cpupools.

Nathan Studer (2):
  Fix sched_priv corruption in ARINC653 alloc_vdata.
  Fix NULL pointer dereference in ARINC653 free_vdata.

 xen/common/sched_arinc653.c |   19 ++++++++++++-------
 1 file changed, 12 insertions(+), 7 deletions(-)

-- 
1.7.9.5

             reply	other threads:[~2013-10-31 20:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-31 20:47 Nathan Studer [this message]
2013-10-31 20:47 ` [PATCH 1/2] Fix sched_priv corruption in ARINC653 alloc_vdata Nathan Studer
2013-11-01 13:53   ` Andrew Cooper
2013-11-03 23:07     ` Nate Studer
2013-11-04 15:49   ` George Dunlap
2013-10-31 20:47 ` [PATCH 2/2] Fix NULL pointer dereference in ARINC653 free_vdata Nathan Studer
2013-11-01 13:56   ` Andrew Cooper
2013-11-01 14:13     ` George Dunlap
2013-11-01 14:17       ` Andrew Cooper
2013-11-03 23:01       ` Nate Studer
2013-11-04 10:46         ` George Dunlap
2013-11-04 10:55           ` Ian Campbell
2013-11-04 15:15           ` Jan Beulich

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=1383252473-3067-1-git-send-email-nate.studer@dornerworks.com \
    --to=nate.studer@dornerworks.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=robert.vanvossen@dornerworks.com \
    --cc=smartin@milliways.cl \
    --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).