All of lore.kernel.org
 help / color / mirror / Atom feed
* Wrong cpupool handling
@ 2014-11-11 12:18 Dietmar Hahn
  2014-11-11 14:17 ` Juergen Gross
  2014-11-11 14:21 ` Juergen Gross
  0 siblings, 2 replies; 6+ messages in thread
From: Dietmar Hahn @ 2014-11-11 12:18 UTC (permalink / raw)
  To: xen-devel; +Cc: jgross

Hi list,

When creating a cpupool, starting and destroying a guest within this pool,
then removing this pool doesn't work because of EBUSY.

It seems the cause of this behavior is the commit
bac6334b51d9bcfe57ecf4a4cb5288348fcf044a.

In domain_kill() the function sched_move_domain() gets called changing the
d->cpupool pointer to the new cpupool without incrementing/decrementing the
counters "n_dom" of the new/old cpupool.

This leads to decrementing the wrong  cpupool0->n_dom counter when
cpupool_rm_domain() gets called at the end and my own cpupool can't be
destroyed because n_dom = 1!

I don't have a fast patch because I'am not enough familiar with the code
this time but I think it should be fixed for 4.5.

Dietmar.


-- 
Company details: http://ts.fujitsu.com/imprint.html

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2014-11-12 10:37 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-11-11 12:18 Wrong cpupool handling Dietmar Hahn
2014-11-11 14:17 ` Juergen Gross
2014-11-11 14:21 ` Juergen Gross
2014-11-12  9:53   ` Dietmar Hahn
2014-11-12 10:25     ` Juergen Gross
2014-11-12 10:37       ` Dietmar Hahn

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.