From: "Namjae Jeon" <namjae.jeon@samsung.com>
To: "'Linus Torvalds'" <torvalds@linux-foundation.org>
Cc: <linux-kernel@vger.kernel.org>,
"'Sungjong Seo'" <sj1557.seo@samsung.com>
Subject: [GIT PULL] exfat update for 5.14-rc1
Date: Mon, 5 Jul 2021 12:27:18 +0900 [thread overview]
Message-ID: <002c01d7714d$a8699070$f93cb150$@samsung.com> (raw)
In-Reply-To: CGME20210705032718epcas1p2a88bc622479d0881c7c63fb201f05c32@epcas1p2.samsung.com
Hi Linus,
This is exfat update pull request for v5.14-rc1. I add description of
this pull request on below. Please pull exfat with following ones.
Thanks!
The following changes since commit 62fb9874f5da54fdb243003b386128037319b219:
Linux 5.13 (2021-06-27 15:21:11 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/linkinjeon/exfat.git tags/exfat-for-5.14-rc1
for you to fetch changes up to 1e5654de0f51890f88abd409ebf4867782431e81:
exfat: handle wrong stream entry size in exfat_readdir() (2021-07-04 09:33:00 +0900)
----------------------------------------------------------------
Description for this pull request:
- Improved compatibility issue with exfat from some camera vendors.
- Do not need to release root inode on error path.
----------------------------------------------------------------
Chen Li (1):
exfat: avoid incorrectly releasing for root inode
Namjae Jeon (1):
exfat: handle wrong stream entry size in exfat_readdir()
fs/exfat/dir.c | 8 +++++---
fs/exfat/super.c | 2 +-
2 files changed, 6 insertions(+), 4 deletions(-)
next parent reply other threads:[~2021-07-05 3:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210705032718epcas1p2a88bc622479d0881c7c63fb201f05c32@epcas1p2.samsung.com>
2021-07-05 3:27 ` Namjae Jeon [this message]
2021-07-06 19:24 ` [GIT PULL] exfat update for 5.14-rc1 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='002c01d7714d$a8699070$f93cb150$@samsung.com' \
--to=namjae.jeon@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sj1557.seo@samsung.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.