reset got_init after handling FUSE_DESTROY message (#910)

User may still need to mount same fuse filesystem after umounting
it(In this case, the userspace filesystem server needs to keep live),
and after handling FUSE_DESTROY message, new FUSE_INIT message may come,
so need to reset got_init to be zero.

Signed-off-by: Xiaoguang Wang <lege.wang@jaguarmicro.com>

diff --git a/lib/fuse_lowlevel.c b/lib/fuse_lowlevel.c
index 86e49f74a190efae27619e9c0483edcce7dca784..26e56995d4559eab4e25a4f5960b4e5dcd1bf3b2 100644 (file)
--- a/lib/fuse_lowlevel.c
+++ b/lib/fuse_lowlevel.c
@@ -2208,6 +2208,7 @@ static void do_destroy(fuse_req_t req, fuse_ino_t nodeid, const void *inarg)
        (void) inarg;
 
        se->got_destroy = 1;
+       se->got_init = 0;
        if (se->op.destroy)
                se->op.destroy(se->userdata);