[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] [PATCH] (V2) Avoid stale pointer when moving domain to another cpupool


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Juergen Gross <juergen.gross@xxxxxxxxxxxxxx>
  • Date: Wed, 27 Feb 2013 10:43:40 +0100
  • Delivery-date: Wed, 27 Feb 2013 09:54:31 +0000
  • Domainkey-signature: s=s1536a; d=ts.fujitsu.com; c=nofws; q=dns; h=X-SBRSScore:X-IronPort-AV:Received:X-IronPort-AV: Received:Received:Content-Type:MIME-Version:Subject: X-Mercurial-Node:Message-Id:Date:From:To; b=HhxaH7eRezaud+T8m/8BXpQYNPCytjib0qhZA9GYY4qlt/lEPdbRZj+r NNWuXeYzovgAmbYGZka2AyzIYSSqmzYlFdLN0Y7QuwlPw0gp6ktIOxYIR KFh6UJNDQBwBJYXXOs4gACbB3c/stQDYYmU7tULlrbxN4BgP6L9JmBsah xny3NkB13WpE6imelUIysq2AQWfganD0K8RQmBktXKY8I9mHJI7f2QASu YvqfJmRME0Zx+JaCE3VWH5cEFgJIR;
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>

When a domain is moved to another cpupool the scheduler private data pointers
in vcpu and domain structures must never point to an already freed memory
area.

While at it, simplify sched_init_vcpu() by using DOM2OP instead VCPU2OP.

Changes since V1:
- don't use an an own loop for freeing vcpu_data
- free old domain data after unpausing the domain
- simplify sched_init_vcpu (DOM2OP instead VCPU2OP)

Signed-off-by: Juergen Gross <juergen.gross@xxxxxxxxxxxxxx>


1 file changed, 14 insertions(+), 6 deletions(-)
xen/common/schedule.c |   20 ++++++++++++++------


Attachment: xen-staging.hg.patch
Description: Text Data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.