remarkable-linux/drivers/net/xen-netback
Paul Durrant c0fcded2e6 xen-netback: only deinitialized hash if it was initialized
A domain with a frontend that does not implement a control ring has been
seen to cause a crash during domain save. This was apparently because
the call to xenvif_deinit_hash() in xenvif_disconnect_ctrl() is made
regardless of whether a control ring was connected, and hence
xenvif_hash_init() was called.

This patch brings the call to xenvif_deinit_hash() in
xenvif_disconnect_ctrl() inside the if clause that checks whether the
control ring event channel was connected. This is sufficient to ensure
it is only called if xenvif_init_hash() was called previously.

Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
Reported-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Tested-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: Wei Liu <wei.liu2@citrix.com>
Acked-by: Wei Liu <wei.liu2@citrix.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2016-05-20 17:41:18 -04:00
..
common.h xen-netback: add control protocol implementation 2016-05-16 13:35:56 -04:00
hash.c xen-netback: correct length checks on hash copy_ops 2016-05-20 10:51:03 -07:00
interface.c xen-netback: only deinitialized hash if it was initialized 2016-05-20 17:41:18 -04:00
Makefile xen-netback: add control protocol implementation 2016-05-16 13:35:56 -04:00
netback.c xen-netback: use hash value from the frontend 2016-05-16 13:35:56 -04:00
xenbus.c xen-netback: add control ring boilerplate 2016-05-16 13:35:56 -04:00