From: Nikolaus Rath <Nikolaus@rath.org>
To: Linux FS Devel <linux-fsdevel@vger.kernel.org>,
miklos <mszeredi@redhat.com>
Subject: Should FUSE set IO_FLUSHER for the userspace process?
Date: Sun, 18 Sep 2022 12:03:04 +0100 [thread overview]
Message-ID: <87mtaxt05z.fsf@vostro.rath.org> (raw)
Hi,
Should the FUSE kernel driver perhaps set PR_SET_IO_FLUSHER for the FUSE
userspace process daemon when a connection is opened?
If I understand correctly, this is necessary to avoid a deadlocks if the
kernel needs to reclaim memory that has to be written back through FUSE.
I don't think it's possible to do this in userspace, since the process
may lack the necessary capabilities.
Best,
-Nikolaus
--
GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
next reply other threads:[~2022-09-18 11:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 11:03 Nikolaus Rath [this message]
2022-09-18 12:52 ` Should FUSE set IO_FLUSHER for the userspace process? Amir Goldstein
2022-09-19 9:20 ` Miklos Szeredi
2022-10-25 15:38 ` Antonio SJ Musumeci
2022-10-26 11:58 ` Miklos Szeredi
2022-10-26 12:17 ` Miklos Szeredi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mtaxt05z.fsf@vostro.rath.org \
--to=nikolaus@rath.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mszeredi@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).