linux-kernel - Re: [PATCH] FUSE: add the async option for the flush/release operation

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 10 Aug 2016 08:52:06 +0200
From:	Miklos Szeredi <miklos@...redi.hu>
To:	Enke Chen <enkechen@...co.com>
Cc:	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
	"Helios Tsoi (hetsoi)" <hetsoi@...co.com>
Subject: Re: [PATCH] FUSE: add the async option for the flush/release operation

On Wed, Aug 10, 2016 at 5:26 AM, Enke Chen <enkechen@...co.com> wrote:
> Hi, Miklos:
>
> This patch adds the async option for the flush/release operation in FUSE.
>
> The async flush/release option allows a FUSE-based application to be terminated
> without being blocked in the flush/release operation even in the presence of
> complex external interactions. In addition, the async operation can be more
> efficient when a large number of fuse-based files is involved.
>
> ---
> Deadlock Example:
>
>     Process A is a multi-threaded application that interacts with Process B,
>     a FUSE-server.
>
>
>                UNIX-domain socket
>     App (A)  -----------------------  FUSE-server (B)
>        |                                   |
>        |                                   |
>        |                                   |
>        +-----------------------------------+
>                open/flush/release

Why would the fuse server want to communicate with the app (using
other than the filesystem)?

Thanks,
Miklos