From: Dr. David Alan Gilbert Date: Thu, 22 Nov 2018 16:05:09 +0000 (+0000) Subject: virtiofsd: Handle hard reboot X-Git-Url: http://git.maquefel.me/?a=commitdiff_plain;h=e8556f49098b5d95634e592d79a97f761b76c96e;p=qemu.git virtiofsd: Handle hard reboot Handle a mount hard reboot (without unmount) mount we get another 'init' which FUSE doesn't normally expect. Signed-off-by: Dr. David Alan Gilbert Reviewed-by: Daniel P. Berrangé Signed-off-by: Dr. David Alan Gilbert --- diff --git a/tools/virtiofsd/fuse_lowlevel.c b/tools/virtiofsd/fuse_lowlevel.c index 7d742b5a72..65f91dabae 100644 --- a/tools/virtiofsd/fuse_lowlevel.c +++ b/tools/virtiofsd/fuse_lowlevel.c @@ -2433,7 +2433,21 @@ void fuse_session_process_buf_int(struct fuse_session *se, goto reply_err; } } else if (in->opcode == FUSE_INIT || in->opcode == CUSE_INIT) { - goto reply_err; + if (fuse_lowlevel_is_virtio(se)) { + /* + * TODO: This is after a hard reboot typically, we need to do + * a destroy, but we can't reply to this request yet so + * we can't use do_destroy + */ + fuse_log(FUSE_LOG_DEBUG, "%s: reinit\n", __func__); + se->got_destroy = 1; + se->got_init = 0; + if (se->op.destroy) { + se->op.destroy(se->userdata); + } + } else { + goto reply_err; + } } err = EACCES;