From: legezywzh <94814730+legezywzh@users.noreply.github.com>
Date: Thu, 21 Mar 2024 09:02:05 +0000 (+0800)
Subject: reset got_init after handling FUSE_DESTROY message (#910)
X-Git-Tag: fuse-3.17.1-rc0~139
X-Git-Url: http://git.maquefel.me/?a=commitdiff_plain;h=f01d9277cb6faface1d8b048db4eddb71b2f5d78;p=qemu-gpiodev%2Flibfuse.git

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 86e49f7..26e5699 100644
--- 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);