From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux FS Dev Mailing List <linux-fsdevel@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux F2FS Dev Mailing List
<linux-f2fs-devel@lists.sourceforge.net>
Subject: [GIT PULL] f2fs fix for 4.11-rc4
Date: Mon, 20 Mar 2017 13:30:19 -0400 [thread overview]
Message-ID: <20170320173019.GA53763@jaegeuk.local> (raw)
Hi Linus,
Could you please pull the below fixes?
Thanks,
The following changes since commit 97da3854c526d3a6ee05c849c96e48d21527606c:
Linux 4.11-rc3 (2017-03-19 19:09:39 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git tags/for-f2fs-4.11-rc4
for you to fetch changes up to 7041d5d286fb54635f540c1bb3b43980ed65513a:
f2fs: combine nat_bits and free_nid_bitmap cache (2017-03-20 10:00:18 -0400)
----------------------------------------------------------------
Bug fix for f2fs
- Fix performance regression reported by lkp-rebot
- Fix potential data lost after power-cut due to SSR reallocation
----------------------------------------------------------------
Chao Yu (2):
f2fs: skip scanning free nid bitmap of full NAT blocks
f2fs: combine nat_bits and free_nid_bitmap cache
Jaegeuk Kim (3):
f2fs: don't overwrite node block by SSR
f2fs: declare static functions
f2fs: use __set{__clear}_bit_le
fs/f2fs/debug.c | 1 +
fs/f2fs/dir.c | 2 +-
fs/f2fs/f2fs.h | 2 +
fs/f2fs/node.c | 163 ++++++++++++++++++++++++++----------------------------
fs/f2fs/segment.c | 6 ++
5 files changed, 87 insertions(+), 87 deletions(-)
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
reply other threads:[~2017-03-20 17:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170320173019.GA53763@jaegeuk.local \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).