Re: [PATCH 0/2] Prevent re-use of FUSE superblock after force unmount

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Daniil Lunev <dlunev@xxxxxxxxxxxx>
Subject: Re: [PATCH 0/2] Prevent re-use of FUSE superblock after force unmount
From: Miklos Szeredi <miklos@xxxxxxxxxx>
Date: Wed, 11 May 2022 09:07:43 +0200
Cc: linux-fsdevel@xxxxxxxxxxxxxxx, fuse-devel <fuse-devel@xxxxxxxxxxxxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, Alexander Viro <viro@xxxxxxxxxxxxxxxxxx>
In-reply-to: <20220511013057.245827-1-dlunev@chromium.org>

On Wed, 11 May 2022 at 03:31, Daniil Lunev <dlunev@xxxxxxxxxxxx> wrote:
>
> Force unmount of fuse severes the connection between FUSE driver and its
> userspace counterpart.

Why is forced umount being used in the first place?

Thanks,
Miklos

Follow-Ups:
- Re: [PATCH 0/2] Prevent re-use of FUSE superblock after force unmount
  - From: Daniil Lunev

References:
- [PATCH 0/2] Prevent re-use of FUSE superblock after force unmount
  - From: Daniil Lunev

Prev by Date: Re: [PATCHSETS] v14 fsdax-rmap + v11 fsdax-reflink
Next by Date: Re: [PATCH 0/2] Prevent re-use of FUSE superblock after force unmount
Previous by thread: [PATCH 2/2] FUSE: Mark super block defunc on force unmount
Next by thread: Re: [PATCH 0/2] Prevent re-use of FUSE superblock after force unmount
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [NTFS 3] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [NTFS 3] [Samba] [Device Mapper] [CEPH Development]

Powered by Linux