Re: [patch 5/6] frontend device shutdown

[Gerd Hoffmann <kraxel@suse.de>]

> I really don't like that distinction very much (moving to Initialising
> instead of Closed). The problem is really in the backend, which incorrectly
> interprets XenbusStateClosed as a request to completely unregister the
> device. The reason it does this is because the control tools signal that
> destruction should take place by deleting the frontend directory in
> xenstore. This results in xenbus_read_driver_state() returning
> XenbusStateClosed, hence the backend drivers have interpreted that state
> value as a destruction request from the tools.

Ok, that should work fine for the backend side.

But there is another problem on the frontend side:  xenbus_probe_node()
ignores devices which are not in Initializing state, so it doesn't
reprobe devices which are about to disappear.  The next kernel should
probe them, but the frontend state is still Closing (or Closed) ...

I think that was the initial reason to do the jumpback to Initializing
(so the new kexec'ed kernel finds an environment identical to the direct
boot).  That was also the reason to introduce the shutdown_in_progress
flag, so I have some way to avoid re-initializing of the device by the
old kernel.

cheers,
  Gerd

-- 
Gerd Hoffmann <kraxel@suse.de>
http://www.suse.de/~kraxel/julika-dora.jpeg