[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fuse-devel
Subject:    Re: [fuse-devel] "blocking" cleanup code executed at umount
From:       Goswin von Brederlow <goswin-v-b () web ! de>
Date:       2012-01-11 13:10:51
Message-ID: 87mx9ul6zo.fsf () frosties ! localnet
[Download RAW message or body]

Miklos Szeredi <miklos@szeredi.hu> writes:

> Goswin von Brederlow <goswin-v-b@web.de> writes:
>> What about umount? destroy() has no reply so the umount can't wait on
>> that? What does it wait on?
>
> Normally umount cannot wait for the filesystem cleanup, because that way
> an unprivileged filesystem may delay (accidentally or deliberately) the
> unmounter.
>
> For fuseblk we assume that the filesystem daemon is privileged, so it is
> allowed to block umount.
>
> The unprivileged case could be improved so that if the unmounter is also
> unprivileged then it can actually wait for the cleanup.  Not sure if
> that is worth it, though.
>
> Thanks,
> Miklos

That wasn't so much a question of why but of how?

As said destroy() has no reply so what does the kernel wait on?

MfG
        Goswin

------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
fuse-devel mailing list
fuse-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fuse-devel
[prev in list] [next in list] [prev in thread] [next in thread]