linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
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.3
Date: Thu, 11 Jul 2019 10:13:36 -0700	[thread overview]
Message-ID: <20190711171336.GA66396@jaegeuk-macbookpro.roam.corp.google.com> (raw)

Hi Linus,

Could you please consider this pull request?

Thanks,

The following changes since commit e0654264c4806dc436b291294a0fbf9be7571ab6:

  Merge tag 'backlight-next-5.2' of git://git.kernel.org/pub/scm/linux/kernel/git/lee/backlight (2019-05-14 10:45:03 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git tags/f2fs-for-5.3

for you to fetch changes up to 2d008835ec2fcf6eef3285e41e62a5eabd1fe76b:

  f2fs: improve print log in f2fs_sanity_check_ckpt() (2019-07-10 18:44:47 -0700)

----------------------------------------------------------------
f2fs-for-5.3-rc1

In this round, we've introduced native swap file support which can exploit DIO,
enhanced existing checkpoint=disable feature with additional mount option to
tune the triggering condition, and allowed user to preallocate physical blocks
in a pinned file which will be useful to avoid f2fs fragmentation in append-only
workloads. In addition, we've fixed subtle quota corruption issue.

Enhancement:
 - add swap file support which uses DIO
 - allocate blocks for pinned file
 - allow SSR and mount option to enhance checkpoint=disable
 - enhance IPU IOs
 - add more sanity checks such as memory boundary access

Bug fix:
 - quota corruption in very corner case of error-injected SPO case
 - fix root_reserved on remount and some wrong counts
 - add missing fsck flag

Some patches were also introduced to clean up ambiguous i_flags and debugging
messages codes.

----------------------------------------------------------------
Chao Yu (10):
      f2fs: fix to check layout on last valid checkpoint park
      f2fs: add bio cache for IPU
      f2fs: fix to avoid deadloop if data_flush is on
      f2fs: fix to do sanity check on segment bitmap of LFS curseg
      f2fs: fix sparse warning
      f2fs: avoid get_valid_blocks() for cleanup
      f2fs: print kernel message if filesystem is inconsistent
      f2fs: use generic EFSBADCRC/EFSCORRUPTED
      f2fs: set SBI_NEED_FSCK for xattr corruption case
      f2fs: improve print log in f2fs_sanity_check_ckpt()

Daniel Rosenberg (4):
      f2fs: Lower threshold for disable_cp_again
      f2fs: Fix root reserved on remount
      f2fs: Fix accounting for unusable blocks
      f2fs: Add option to limit required GC for checkpoint=disable

Eric Biggers (1):
      f2fs: separate f2fs i_flags from fs_flags and ext4 i_flags

Geert Uytterhoeven (1):
      f2fs: Use DIV_ROUND_UP() instead of open-coding

Heng Xiao (1):
      f2fs: fix to avoid long latency during umount

Jaegeuk Kim (7):
      f2fs: link f2fs quota ops for sysfile
      f2fs: allow ssr block allocation during checkpoint=disable period
      f2fs: add missing sysfs entries in documentation
      f2fs: add a rw_sem to cover quota flag changes
      f2fs: allocate blocks for pinned file
      f2fs: support swap file w/ DIO
      f2fs: allow all the users to pin a file

Joe Perches (1):
      f2fs: introduce f2fs_<level> macros to wrap f2fs_printk()

Kimberly Brown (1):
      f2fs: replace ktype default_attrs with default_groups

Ocean Chen (1):
      f2fs: avoid out-of-range memory access

Park Ju Hyung (1):
      f2fs: always assume that the device is idle under gc_urgent

Qiuyang Sun (1):
      f2fs: ioctl for removing a range from F2FS

Sahitya Tummala (3):
      f2fs: add error prints for debugging mount failure
      f2fs: fix f2fs_show_options to show nodiscard mount option
      f2fs: fix is_idle() check for discard type

Wang Shilong (1):
      f2fs: only set project inherit bit for directory

 Documentation/ABI/testing/sysfs-fs-f2fs |   8 +
 Documentation/filesystems/f2fs.txt      | 133 ++++++-
 fs/f2fs/checkpoint.c                    | 107 +++---
 fs/f2fs/data.c                          | 249 +++++++++++--
 fs/f2fs/debug.c                         |   7 +
 fs/f2fs/dir.c                           |  16 +-
 fs/f2fs/extent_cache.c                  |   7 +-
 fs/f2fs/f2fs.h                          | 129 +++----
 fs/f2fs/file.c                          | 302 ++++++++++------
 fs/f2fs/gc.c                            | 196 +++++++++-
 fs/f2fs/inline.c                        |  16 +-
 fs/f2fs/inode.c                         |  78 ++--
 fs/f2fs/namei.c                         |  10 +-
 fs/f2fs/node.c                          |  38 +-
 fs/f2fs/recovery.c                      |  43 +--
 fs/f2fs/segment.c                       | 170 +++++++--
 fs/f2fs/segment.h                       |  16 +-
 fs/f2fs/super.c                         | 610 +++++++++++++++-----------------
 fs/f2fs/sysfs.c                         |  28 +-
 fs/f2fs/xattr.c                         |  10 +-
 include/trace/events/f2fs.h             |  11 +-
 21 files changed, 1409 insertions(+), 775 deletions(-)


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

             reply	other threads:[~2019-07-11 17:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-11 17:13 Jaegeuk Kim [this message]
2019-07-13  0:40 ` [f2fs-dev] [GIT PULL] f2fs for 5.3 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=20190711171336.GA66396@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).