Although this is a rare situation, it can happen: one worker is currently executing a balloon_inflate, while another is created to handle a deflate. Ouch. Linux fixes that by having a "biglock" mutex wrapping the balloon handler loop, but I'd like to avoid going down that route.Well, workqueue already does it for you: a workqueue can have only one workerat a time.
That pretty much solves my issue then. (I really need to have a look down there) -- Jean-Yves Migeon jeanyves.migeon%free.fr@localhost