From: "Namjae Jeon" <namjae.jeon@samsung.com>
To: "'Sungjong Seo'" <sj1557.seo@samsung.com>
Cc: <linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] exfat: flush dirty metadata in fsync
Date: Mon, 22 Jun 2020 09:27:16 +0900 [thread overview]
Message-ID: <000a01d6482b$e1eb34d0$a5c19e70$@samsung.com> (raw)
In-Reply-To: <1592480606-14657-1-git-send-email-sj1557.seo@samsung.com>
> generic_file_fsync() exfat used could not guarantee the consistency of a file because it has flushed
> not dirty metadata but only dirty data pages for a file.
>
> Instead of that, use exfat_file_fsync() for files and directories so that it guarantees to commit both
> the metadata and data pages for a file.
>
> Signed-off-by: Sungjong Seo <sj1557.seo@samsung.com>
Pushed it into exfat #dev. Thanks!
prev parent reply other threads:[~2020-06-22 0:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200618121007epcas1p1aa0f24b361e0232913bf7477ee0a92c8@epcas1p1.samsung.com>
2020-06-18 11:43 ` [PATCH] exfat: flush dirty metadata in fsync Sungjong Seo
2020-06-22 0:27 ` Namjae Jeon [this message]
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='000a01d6482b$e1eb34d0$a5c19e70$@samsung.com' \
--to=namjae.jeon@samsung.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sj1557.seo@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;
as well as URLs for NNTP newsgroup(s).