public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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.9-rc9
Date: Wed, 7 Oct 2020 17:36:03 +0900	[thread overview]
Message-ID: <009901d69c84$e422f280$ac68d780$@samsung.com> (raw)
In-Reply-To: CGME20201007083603epcas1p22050f982bbf149ad060b723d763de1b3@epcas1p2.samsung.com

Hi Linus,

This is exfat fixes pull request for v5.9-rc9. I add description of
this pull request on below. Please pull exfat with following fixes.

Thanks!

The following changes since commit 549738f15da0e5a00275977623be199fbbf7df50:

  Linux 5.9-rc8 (2020-10-04 16:04:34 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/linkinjeon/exfat.git tags/exfat-for-5.9-rc9

for you to fetch changes up to 8ff006e57ad3a25f909c456d053aa498b6673a39:

  exfat: fix use of uninitialized spinlock on error path (2020-10-07 14:27:13 +0900)

----------------------------------------------------------------
Description for this pull request:
  - Fix use of uninitialized spinlock on error path.
  - Fix missing err assignment in exfat_build_inode().

----------------------------------------------------------------
Namjae Jeon (1):
      exfat: fix use of uninitialized spinlock on error path

Tetsuhiro Kohada (1):
      exfat: fix pointer error checking

 fs/exfat/cache.c    | 11 -----------
 fs/exfat/exfat_fs.h |  3 ++-
 fs/exfat/inode.c    |  2 --
 fs/exfat/namei.c    | 13 ++++++-------
 fs/exfat/super.c    |  5 ++++-
 5 files changed, 12 insertions(+), 22 deletions(-)


       reply	other threads:[~2020-10-07  8:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20201007083603epcas1p22050f982bbf149ad060b723d763de1b3@epcas1p2.samsung.com>
2020-10-07  8:36 ` Namjae Jeon [this message]
2020-10-08 19:20   ` [GIT PULL] exfat fixes for 5.9-rc9 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='009901d69c84$e422f280$ac68d780$@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