From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux F2FS Dev Mailing List
<linux-f2fs-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] f2fs fix for 5.13-rc1
Date: Fri, 14 May 2021 03:14:12 -0700 [thread overview]
Message-ID: <YJ5NdFzVb1f9aVqG@google.com> (raw)
Hi Linus,
Could you please consider this pull request?
Thanks,
The following changes since commit 6efb943b8616ec53a5e444193dccf1af9ad627b5:
Linux 5.13-rc1 (2021-05-09 14:17:44 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git tags/f2fs-5.13-rc1-fix
for you to fetch changes up to f395183f9544ba2f56b25938d6ea7042bd873521:
f2fs: return EINVAL for hole cases in swap file (2021-05-12 07:38:00 -0700)
----------------------------------------------------------------
f2fs-5.13-rc1-fix
This series of patches fix some critical bugs such as memory leak in compression
flows, kernel panic when handling errors, and swapon failure due to newly added
condition check.
----------------------------------------------------------------
Chao Yu (3):
f2fs: compress: fix to free compress page correctly
f2fs: compress: fix race condition of overwrite vs truncate
f2fs: compress: fix to assign cc.cluster_idx correctly
Jaegeuk Kim (4):
f2fs: avoid null pointer access when handling IPU error
f2fs: support iflag change given the mask
f2fs: avoid swapon failure by giving a warning first
f2fs: return EINVAL for hole cases in swap file
fs/f2fs/compress.c | 55 +++++++++++++++++++++++-------------------------------
fs/f2fs/data.c | 39 +++++++++++++++++++++++++++-----------
fs/f2fs/f2fs.h | 2 +-
fs/f2fs/file.c | 3 ++-
fs/f2fs/segment.c | 4 ++--
5 files changed, 56 insertions(+), 47 deletions(-)
next reply other threads:[~2021-05-14 10:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 10:14 Jaegeuk Kim [this message]
2021-05-14 18:00 ` [f2fs-dev] " 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=YJ5NdFzVb1f9aVqG@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
Powered by JetHome