All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Jan Kara <jack@suse.cz>
Cc: JunChao Sun <sunjunchao2870@gmail.com>,
	Miklos Szeredi <miklos@szeredi.hu>,
	linux-fsdevel@vger.kernel.org
Subject: Re: Is is reasonable to support quota in fuse?
Date: Wed, 5 Jun 2024 21:53:46 +0200	[thread overview]
Message-ID: <20240605195346.GC4182@mit.edu> (raw)
In-Reply-To: <20240605102945.q4nu67xpdwfziiqd@quack3>

On Wed, Jun 05, 2024 at 12:29:45PM +0200, Jan Kara wrote:
> 
> But that's why I'm asking for usecases. For some usecases it may be fine
> that in case of unclean shutdown you run quotacheck program to update quota
> information based on current usage - non-journalling filesystems use this
> method. So where do you want to use quotas on a FUSE filesystem?

Something else to consider is whether you want to allow the user to
query the current quota information (e.g., the "quota" command), and
whether you want the system administrator to be able to set quota
limits, and whether you expect that when the soft quota limits are
exceeded that warnings get written to the user's tty.  All of this
would mean that the kernel fuse driver would need changes, and the
kernel<->userspae FUSE protocol would need to be extended as well.
And at that pointm you really want to get the FUSE maintainer
involved, since the FUSE protocol is somethign which is used on other
OS's (e.g., Windows, MacOS, etc.)

As Jan put it, it's all in the use cases that you expect to be able to
support.  If you just want quota to be tracked, and for certain writes
to return EDQUOT, that's one thing.  If you want the full Linux quota
user experience, that's quite another.

Cheers,

						- Ted

  reply	other threads:[~2024-06-05 19:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-03 11:36 Is is reasonable to support quota in fuse? JunChao Sun
2024-06-04  6:03 ` JunChao Sun
2024-06-04  6:40 ` Miklos Szeredi
2024-06-04  6:54   ` JunChao Sun
2024-06-04  9:27     ` Jan Kara
2024-06-04 13:49       ` JunChao Sun
2024-06-05 10:29         ` Jan Kara
2024-06-05 19:53           ` Theodore Ts'o [this message]
2024-06-06  3:58             ` JunChao Sun
2024-06-06  3:14           ` JunChao Sun
2024-06-06 16:10             ` Jan Kara
2024-06-07 12:11               ` JunChao Sun
2024-06-06 15:17 ` Darrick J. Wong
2024-06-07 11:10   ` JunChao Sun

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=20240605195346.GC4182@mit.edu \
    --to=tytso@mit.edu \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=sunjunchao2870@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.