forked from Minki/linux
fuse: retire block-device-based superblock on force unmount
Force unmount of FUSE severes the connection with the user space, even if there are still open files. Subsequent remount tries to re-use the superblock held by the open files, which is meaningless in the FUSE case after disconnect - reused super block doesn't have userspace counterpart attached to it and is incapable of doing any IO. This patch adds the functionality only for the block-device-based supers, since the primary use case of the feature is to gracefully handle force unmount of external devices, mounted with FUSE. This can be further extended to cover all superblocks, if the need arises. Signed-off-by: Daniil Lunev <dlunev@chromium.org> Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
This commit is contained in:
parent
04b9407197
commit
247861c325
@ -482,8 +482,14 @@ static void fuse_umount_begin(struct super_block *sb)
|
||||
{
|
||||
struct fuse_conn *fc = get_fuse_conn_super(sb);
|
||||
|
||||
if (!fc->no_force_umount)
|
||||
fuse_abort_conn(fc);
|
||||
if (fc->no_force_umount)
|
||||
return;
|
||||
|
||||
fuse_abort_conn(fc);
|
||||
|
||||
// Only retire block-device-based superblocks.
|
||||
if (sb->s_bdev != NULL)
|
||||
retire_super(sb);
|
||||
}
|
||||
|
||||
static void fuse_send_destroy(struct fuse_mount *fm)
|
||||
|
Loading…
Reference in New Issue
Block a user