From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux F2FS Dev Mailing List
<linux-f2fs-devel@lists.sourceforge.net>
Subject: [f2fs-dev] [GIT PULL] f2fs for 5.5
Date: Wed, 27 Nov 2019 12:01:38 -0800 [thread overview]
Message-ID: <20191127200138.GA47793@jaegeuk-macbookpro.roam.corp.google.com> (raw)
Hi Linus,
Could you please consider this pull request?
The following changes since commit b145b0eb2031a620ca010174240963e4d2c6ce26:
Merge tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm (2019-10-04 11:17:51 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git tags/f2fs-for-5.5
for you to fetch changes up to 803e74be04b32f7785742dcabfc62116718fbb06:
f2fs: stop GC when the victim becomes fully valid (2019-11-25 10:01:28 -0800)
----------------------------------------------------------------
f2fs-for-5.5-rc1
In this round, we've introduced fairly small number of patches as below.
Enhancement:
- improve the in-place-update IO flow
- allocate segment to guarantee no GC for pinned files
Bug fix:
- fix updatetime in lazytime mode
- potential memory leak in f2fs_listxattr
- record parent inode number in rename2 correctly
- fix deadlock in f2fs_gc along with atomic writes
- avoid needless data migration in GC
----------------------------------------------------------------
Chao Yu (6):
f2fs: fix to update time in lazytime mode
f2fs: cache global IPU bio
f2fs: fix wrong description in document
f2fs: fix to update dir's i_pino during cross_rename
f2fs: fix potential overflow
f2fs: show f2fs instance in printk_ratelimited
Chengguang Xu (1):
f2fs: choose hardlimit when softlimit is larger than hardlimit in f2fs_statfs_project()
Chengguang Xu via Linux-f2fs-devel (1):
f2fs: mark recovery flag correctly in read_raw_super_block()
Jaegeuk Kim (4):
f2fs: avoid kernel panic on corruption test
f2fs: support aligned pinned file
f2fs: expose main_blkaddr in sysfs
f2fs: stop GC when the victim becomes fully valid
Qiuyang Sun (2):
f2fs: update multi-dev metadata in resize_fs
f2fs: check total_segments from devices in raw_super
Randall Huang (1):
f2fs: fix to avoid memory leakage in f2fs_listxattr
Sahitya Tummala (1):
f2fs: Fix deadlock in f2fs_gc() context during atomic files handling
Documentation/ABI/testing/sysfs-fs-f2fs | 6 +
Documentation/filesystems/f2fs.txt | 5 +-
fs/f2fs/checkpoint.c | 2 +-
fs/f2fs/data.c | 190 +++++++++++++++++++++++++-------
fs/f2fs/dir.c | 7 +-
fs/f2fs/f2fs.h | 63 +++++++----
fs/f2fs/file.c | 47 ++++++--
fs/f2fs/gc.c | 46 +++++++-
fs/f2fs/inode.c | 8 +-
fs/f2fs/namei.c | 15 ++-
fs/f2fs/node.c | 3 +-
fs/f2fs/recovery.c | 2 +-
fs/f2fs/segment.c | 64 ++++++++---
fs/f2fs/segment.h | 2 +
fs/f2fs/super.c | 50 +++++++--
fs/f2fs/sysfs.c | 4 +
fs/f2fs/xattr.c | 14 ++-
17 files changed, 421 insertions(+), 107 deletions(-)
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next reply other threads:[~2019-11-27 20:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 20:01 Jaegeuk Kim [this message]
2019-11-30 19:40 ` [f2fs-dev] [GIT PULL] f2fs for 5.5 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=20191127200138.GA47793@jaegeuk-macbookpro.roam.corp.google.com \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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).