mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: David Timber <dxdt@dev.snart.me>
Cc: linux-kernel@vger.kernel.org,  linux-fsdevel@vger.kernel.org
Subject: Re: [RFC PATCH] fat: add noflush mount option
Date: Tue, 25 Aug 2026 13:31:54 +0900	[thread overview]
Message-ID: <87ecfmrfb9.fsf@mail.parknet.co.jp> (raw)
In-Reply-To: <787aea79-beb0-4f29-bb67-ee57f6c654c4@dev.snart.me>

David Timber <dxdt@dev.snart.me> writes:


[...]

>>> @@ -1110,6 +1114,7 @@ const struct fs_parameter_spec fat_param_spec[] = {
>>>  	fsparam_flag	("debug",	Opt_debug),
>>>  	fsparam_flag	("sys_immutable", Opt_immutable),
>>>  	fsparam_flag	("flush",	Opt_flush),
>>> +	fsparam_flag	("noflush",	Opt_noflush),
>> fsparam_flag() is not including the "noflush" too?
> I think I should use fsparam_flag_no() here. My bad.
>
> It seems that you don't object to the idea. That's a good start!
>
> If we want to do this, the
> documentation(Documentation/filesystems/vfat.rst and mount(8)) should be
> updated, too. fyi, `udisksctl mount -o` won't accept "noflush" so
> that'll have to be fixed, too. Also have to make sure if "noflush" is
> used in fstab, udisks2 overrides the system default settings.

Well, with a your patch, just remounting without "flush" option doesn't
remove flush?  And this is a user visible change more or less, so if
there is an objection from users, then it will be dropped.

Thanks.
-- 
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>

  reply	other threads:[~2026-08-25  4:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-22 17:37 David Timber
2026-08-24  9:45 ` OGAWA Hirofumi
2026-08-25  1:10   ` David Timber
2026-08-25  4:31     ` OGAWA Hirofumi [this message]
2026-08-26  4:22       ` David Timber
2026-08-26  7:21         ` OGAWA Hirofumi
2026-08-26  8:00           ` David Timber
2026-08-26  8:57             ` OGAWA Hirofumi
2026-08-25  5:51 ` Christoph Hellwig
2026-08-26  4:13   ` David Timber
2026-08-26  4:40     ` Christoph Hellwig

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=87ecfmrfb9.fsf@mail.parknet.co.jp \
    --to=hirofumi@mail.parknet.co.jp \
    --cc=dxdt@dev.snart.me \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®