From: "Namjae Jeon" <namjae.jeon@samsung.com>
To: "'Linus Torvalds'" <torvalds@linux-foundation.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] exfat fixes for 5.8-rc4
Date: Tue, 30 Jun 2020 12:05:44 +0900 [thread overview]
Message-ID: <002f01d64e8b$586fa220$094ee660$@samsung.com> (raw)
In-Reply-To: CGME20200630030544epcas1p255f59b5d5e2c82219c37fc5b341b1e67@epcas1p2.samsung.com
Hi Linus,
This is exfat fixes pull request for v5.8-rc4. I add description of
this pull request on below. Please pull exfat with following fixes.
Thanks!
The following changes since commit 9ebcfadb0610322ac537dd7aa5d9cbc2b2894c68:
Linux 5.8-rc3 (2020-06-28 15:00:24 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/linkinjeon/exfat.git tags/exfat-for-5.8-rc4
for you to fetch changes up to 5267456e953fd8c5abd8e278b1cc6a9f9027ac0a:
exfat: flush dirty metadata in fsync (2020-06-29 17:11:18 +0900)
----------------------------------------------------------------
Description for this pull request:
- Zero out unused characters of FileName field to avoid a complaint from some fsck tool.
- Fix memory leak on error paths.
- Fix unnecessary VOL_DIRTY set when calling rmdir on non-empty directory.
- Call sync_filesystem() for read-only remount(Fix generic/452 test in xfstests)
- Add own fsync() to flush dirty metadata.
----------------------------------------------------------------
Dan Carpenter (1):
exfat: add missing brelse() calls on error paths
Hyeongseok.Kim (1):
exfat: Set the unused characters of FileName field to the value 0000h
Hyunchul Lee (1):
exfat: call sync_filesystem for read-only remount
Namjae Jeon (1):
exfat: move setting VOL_DIRTY over exfat_remove_entries()
Sungjong Seo (1):
exfat: flush dirty metadata in fsync
fs/exfat/dir.c | 12 +++++++-----
fs/exfat/exfat_fs.h | 1 +
fs/exfat/file.c | 19 ++++++++++++++++++-
fs/exfat/namei.c | 14 +++++++++++---
fs/exfat/super.c | 10 ++++++++++
5 files changed, 47 insertions(+), 9 deletions(-)
next parent reply other threads:[~2020-06-30 3:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200630030544epcas1p255f59b5d5e2c82219c37fc5b341b1e67@epcas1p2.samsung.com>
2020-06-30 3:05 ` Namjae Jeon [this message]
2020-07-01 19:10 ` [GIT PULL] exfat fixes for 5.8-rc4 pr-tracker-bot
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='002f01d64e8b$586fa220$094ee660$@samsung.com' \
--to=namjae.jeon@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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