Linux filesystem development
 help / color / mirror / Atom feed
From: David Timber <dxdt@dev.snart.me>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC PATCH] fat: add noflush mount option
Date: Wed, 26 Aug 2026 17:00:04 +0900	[thread overview]
Message-ID: <75c9377d-33ee-472c-911f-33a3e1f661d6@dev.snart.me> (raw)
In-Reply-To: <875x0xpcsr.fsf@mail.parknet.co.jp>

On 8/26/26 16:21, OGAWA Hirofumi wrote:
> David Timber <dxdt@dev.snart.me> writes:
>
>> On 8/25/26 13:31, OGAWA Hirofumi wrote:
>>> Well, with a your patch, just remounting without "flush" option doesn't
>>> remove flush?
>> fat_parse_param() doesn't behave like other fs. The current
>> implementation only accepts rw and ro for reconfig. So the option cannot
>> be flipped up and down at will.
> I meant with your patch. With your patch, it updates flush to current
> option set, right? And default flush=false, I may missing something
> though.
Of course. It shouldn't change the default behaviour. When mounting, if
"flush" is in the mount options, it must be honored UNLESS "noflush" is
also specified later in the sequences. If neither "flush" or "noflush"
is specified, then it's not set at all. Specifying "noflush" only should
be no-op.

If the patch doesn't behave like that, that'd be my mistake and should
be fixed.

When doing "mount -o remount,..." the patch changes the existing
behaviour so that "flush" and "noflush" are now honored. Regardless of
the previous sbi config, for "-o remount,flush" -> it always sets flush.
For "-o remount,noflush" -> always clear flush.

Hope that cleared things up.

  reply	other threads:[~2026-08-26  8:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-22 17:37 [RFC PATCH] fat: add noflush mount option David Timber
2026-08-24  9:45 ` OGAWA Hirofumi
2026-08-25  1:10   ` David Timber
2026-08-25  4:31     ` OGAWA Hirofumi
2026-08-26  4:22       ` David Timber
2026-08-26  7:21         ` OGAWA Hirofumi
2026-08-26  8:00           ` David Timber [this message]
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=75c9377d-33ee-472c-911f-33a3e1f661d6@dev.snart.me \
    --to=dxdt@dev.snart.me \
    --cc=hirofumi@mail.parknet.co.jp \
    --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