[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <YmbSOkjjP5ekfcGk@google.com>
Date: Mon, 25 Apr 2022 09:54:18 -0700
From: Jaegeuk Kim <jaegeuk@...nel.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux F2FS Dev Mailing List
<linux-f2fs-devel@...ts.sourceforge.net>
Subject: [GIT PULL] f2fs fix for 5.18
Hi Linus,
Could you please consider this pull request?
Thanks,
The following changes since commit ce522ba9ef7e2d9fb22a39eb3371c0c64e2a433e:
Linux 5.18-rc2 (2022-04-10 14:21:36 -1000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git tags/f2fs-fix-5.18
for you to fetch changes up to 4d8ec91208196e0e19195f1e7d6be9de5873f242:
f2fs: should not truncate blocks during roll-forward recovery (2022-04-21 18:57:09 -0700)
----------------------------------------------------------------
f2fs-fix-5.18
This includes major bug fixes introduced in 5.18-rc1 and 5.17+.
- Remove obsolete whint_mode (5.18-rc1)
- Fix IO split issue caused by op_flags change in f2fs (5.18-rc1)
- Fix a wrong condition check to detect IO failure loop (5.18-rc1)
- Fix wrong data truncation during roll-forward (5.17+)
----------------------------------------------------------------
Jaegeuk Kim (4):
f2fs: remove obsolete whint_mode
f2fs: keep io_flags to avoid IO split due to different op_flags in two fio holders
f2fs: fix wrong condition check when failing metapage read
f2fs: should not truncate blocks during roll-forward recovery
Documentation/filesystems/f2fs.rst | 70 ----------------------------
fs/f2fs/checkpoint.c | 6 +--
fs/f2fs/data.c | 33 ++++++++-----
fs/f2fs/f2fs.h | 9 ----
fs/f2fs/inode.c | 3 +-
fs/f2fs/segment.c | 95 --------------------------------------
fs/f2fs/super.c | 32 +------------
7 files changed, 27 insertions(+), 221 deletions(-)
Powered by blists - more mailing lists