lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 13 Aug 2014 14:44:14 +0200 From: Miklos Szeredi <miklos@...redi.hu> To: Maxim Patlasov <MPatlasov@...allels.com> Cc: fuse-devel <fuse-devel@...ts.sourceforge.net>, Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: [PATCH 0/5] fuse: close file synchronously (v2) On Fri, Jun 6, 2014 at 3:27 PM, Maxim Patlasov <MPatlasov@...allels.com> wrote: > Hi, > > There is a long-standing demand for synchronous behaviour of fuse_release: > > http://sourceforge.net/mailarchive/message.php?msg_id=19343889 > http://sourceforge.net/mailarchive/message.php?msg_id=29814693 > > A year ago Avati and me explained why such a feature would be useful: > > http://sourceforge.net/mailarchive/message.php?msg_id=29889055 > http://sourceforge.net/mailarchive/message.php?msg_id=29867423 > > In short, the problem is that fuse_release (that's called on last user > close(2)) sends FUSE_RELEASE to userspace and returns without waiting for > ACK from userspace. Consequently, there is a gap when user regards the > file released while userspace fuse is still working on it. An attempt to > access the file from another node leads to complicated synchronization > problems because the first node still "holds" the file. Tying RELEASE to close(2) is not going to work. Look at all the places that call fput() (or fdput() in recent kernels), those are all potential triggers for RELEASE, some realistic, some not quite, but all are certainly places that a synchronous release could block *instead* of close. Which just means, that close will still be asynchronous with release some of the time. So it's not clear to me what is to be gained from this patchset. Thanks, Miklos -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists