From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out5-smtp.messagingengine.com ([66.111.4.29]:37513 "EHLO out5-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934351AbcKWXLq (ORCPT ); Wed, 23 Nov 2016 18:11:46 -0500 From: Nikolaus Rath To: linux-kernel , linux-fsdevel , Miklos Szeredi Cc: fuse-devel Subject: fuse: feasible to distinguish between umount and abort? Date: Wed, 23 Nov 2016 15:11:43 -0800 Message-ID: <87a8cp3i6o.fsf@thinkpad.rath.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Hello, Currently, both a call to umount(2) and writing "1" to /sys/fs/fuse/connections/NNN/abort will put the /dev/fuse fd into the same state: reading from it returns ENODEV, and polling on it returns POLLERR. This causes problems for filesystems that want to ensure that the mountpoint is free when they exit. If accessing the device fd gives the above errors, they have to do an additional check to determine if they still need to unmount the mountpoint. This is difficult to do without race conditions (think of someone unmounting and immediately re-starting a new filesystem instance). Would it be possible to change the behavior of the /dev/fuse fd so that userspace can distinguish between a regular umount and use of the /sys/fs/fuse abort)? Best, -Nikolaus --=20 GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F =C2=BBTime flies like an arrow, fruit flies like a Banana.=C2= =AB