From: "Sungjong Seo" <sj1557.seo@samsung.com>
To: "'Hyunchul Lee'" <hyc.lee@gmail.com>,
"'Namjae Jeon'" <namjae.jeon@samsung.com>
Cc: <linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v2] exfat: call sync_filesystem for read-only remount
Date: Wed, 17 Jun 2020 17:10:28 +0900 [thread overview]
Message-ID: <42fb01d6447e$c372d860$4a588920$@samsung.com> (raw)
In-Reply-To: <20200616053445.18125-1-hyc.lee@gmail.com>
> We need to commit dirty metadata and pages to disk before remounting exfat
> as read-only.
>
> This fixes a failure in xfstests generic/452
>
> generic/452 does the following:
> cp something <exfat>/
> mount -o remount,ro <exfat>
>
> the <exfat>/something is corrupted. because while exfat is remounted as
> read-only, exfat doesn't have a chance to commit metadata and vfs
> invalidates page caches in a block device.
>
> Signed-off-by: Hyunchul Lee <hyc.lee@gmail.com>
Acked-by: Sungjong Seo <sj1557.seo@samsung.com>
> ---
> Changes from v1:
> - Does not check the return value of sync_filesystem to
> allow to change from "rw" to "ro" even when this function
> fails.
> - Add the detailed explanation why generic/452 fails
>
> fs/exfat/super.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/fs/exfat/super.c b/fs/exfat/super.c index
> e650e65536f8..253a92460d52 100644
> --- a/fs/exfat/super.c
> +++ b/fs/exfat/super.c
> @@ -693,10 +693,20 @@ static void exfat_free(struct fs_context *fc)
> }
> }
>
> +static int exfat_reconfigure(struct fs_context *fc) {
> + fc->sb_flags |= SB_NODIRATIME;
> +
> + /* volume flag will be updated in exfat_sync_fs */
> + sync_filesystem(fc->root->d_sb);
> + return 0;
> +}
> +
> static const struct fs_context_operations exfat_context_ops = {
> .parse_param = exfat_parse_param,
> .get_tree = exfat_get_tree,
> .free = exfat_free,
> + .reconfigure = exfat_reconfigure,
> };
>
> static int exfat_init_fs_context(struct fs_context *fc)
> --
> 2.17.1
next prev parent reply other threads:[~2020-06-17 8:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200616053459epcas1p4e7a4908eda3785d6f5cbb71150cbe50b@epcas1p4.samsung.com>
2020-06-16 5:34 ` [PATCH v2] exfat: call sync_filesystem for read-only remount Hyunchul Lee
2020-06-17 8:10 ` Sungjong Seo [this message]
2020-06-17 8:40 ` Namjae Jeon
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='42fb01d6447e$c372d860$4a588920$@samsung.com' \
--to=sj1557.seo@samsung.com \
--cc=hyc.lee@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namjae.jeon@samsung.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