diff options
author | legezywzh <94814730+legezywzh@users.noreply.github.com> | 2024-03-21 17:02:05 +0800 |
---|---|---|
committer | GitHub <noreply@github.com> | 2024-03-21 10:02:05 +0100 |
commit | f01d9277cb6faface1d8b048db4eddb71b2f5d78 (patch) | |
tree | 5d7ee31eca50d5c1a02dd0491a53f4288eb6387d | |
parent | e547a66566900f6b17bc9515beb60a304aef6466 (diff) | |
download | libfuse-f01d9277cb6faface1d8b048db4eddb71b2f5d78.tar.gz |
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>
-rw-r--r-- | lib/fuse_lowlevel.c | 1 |
1 files changed, 1 insertions, 0 deletions
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); |