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-rc7
Date: Wed, 22 Jul 2020 13:57:47 +0900 [thread overview]
Message-ID: <003601d65fe4$a4d20da0$ee7628e0$@samsung.com> (raw)
In-Reply-To: <CGME20200722045747epcas1p3304644dafc49b5cc877454e51c6ec00a@epcas1p3.samsung.com>
Hi Linus,
This is exfat fixes pull request for v5.8-rc7. I add description of
this pull request on below. Please pull exfat with following fixes.
Thanks!
The following changes since commit ba47d845d715a010f7b51f6f89bae32845e6acb7:
Linux 5.8-rc6 (2020-07-19 15:41:18 -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-rc7
for you to fetch changes up to db415f7aae07cadcabd5d2a659f8ad825c905299:
exfat: fix name_hash computation on big endian systems (2020-07-21 10:44:19 +0900)
----------------------------------------------------------------
Description for this pull request:
- fix overflow issue at sector calculation.
- fix wrong hint_stat initialization.
- fix wrong size update of stream entry.
- fix endianness of upname in name_hash computation.
----------------------------------------------------------------
Hyeongseok Kim (1):
exfat: fix wrong size update of stream entry by typo
Ilya Ponetayev (1):
exfat: fix name_hash computation on big endian systems
Namjae Jeon (2):
exfat: fix overflow issue in exfat_cluster_to_sector()
exfat: fix wrong hint_stat initialization in exfat_find_dir_entry()
fs/exfat/dir.c | 2 +-
fs/exfat/exfat_fs.h | 2 +-
fs/exfat/file.c | 2 +-
fs/exfat/nls.c | 8 ++++----
4 files changed, 7 insertions(+), 7 deletions(-)
next parent reply other threads:[~2020-07-22 4:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200722045747epcas1p3304644dafc49b5cc877454e51c6ec00a@epcas1p3.samsung.com>
2020-07-22 4:57 ` Namjae Jeon [this message]
2020-07-23 0:35 ` 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='003601d65fe4$a4d20da0$ee7628e0$@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
all inboxes | Powered by JetHome®