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: [GIT PULL] f2fs for 5.6-rc6
Date: Wed, 11 Mar 2020 09:27:35 -0700 [thread overview]
Message-ID: <20200311162735.GA152176@google.com> (raw)
Hi Linus,
Sorry for late pull request. Could you please consider this?
Thanks,
The following changes since commit b19e8c68470385dd2c5440876591fddb02c8c402:
Merge tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux (2020-02-13 14:36:57 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git tags/f2fs-for-5.6-rc6
for you to fetch changes up to 2536ac6872e5265b4d9d263122cee02e3d5cae1d:
f2fs: allow to clear F2FS_COMPR_FL flag (2020-03-11 08:25:38 -0700)
----------------------------------------------------------------
f2fs-for-5.6-rc6
Some major bug fixes wrt compression:
- compressed block count
- memory access and leak
- remove obsolete fields
- flag controls
And some others:
- replace rwsem with spinlock
- potential deadlock
----------------------------------------------------------------
Chao Yu (14):
f2fs: fix to wait all node page writeback
f2fs: fix to avoid NULL pointer dereference
f2fs: recycle unused compress_data.chksum feild
f2fs: add missing function name in kernel message
f2fs: fix to avoid potential deadlock
f2fs: fix to check i_compr_blocks correctly
f2fs: cover last_disk_size update with spinlock
f2fs: remove i_sem lock coverage in f2fs_setxattr()
f2fs: fix inconsistent comments
f2fs: fix to avoid using uninitialized variable
f2fs: fix to avoid use-after-free in f2fs_write_multi_pages()
f2fs: fix to account compressed inode correctly
f2fs: fix to check dirty pages during compressed inode conversion
f2fs: allow to clear F2FS_COMPR_FL flag
Eric Biggers (1):
f2fs: fix leaking uninitialized memory in compressed clusters
Jaegeuk Kim (1):
f2fs: fix wrong check on F2FS_IOC_FSSETXATTR
Sahitya Tummala (1):
f2fs: fix the panic in do_checkpoint()
fs/f2fs/checkpoint.c | 34 +++++++++++-----------------------
fs/f2fs/compress.c | 24 ++++++++++++++----------
fs/f2fs/data.c | 23 ++++++++---------------
fs/f2fs/f2fs.h | 18 ++++++++++--------
fs/f2fs/file.c | 40 +++++++++++++++++++++++++---------------
fs/f2fs/gc.c | 5 ++++-
fs/f2fs/inode.c | 25 +++++++++++++++++++++----
fs/f2fs/namei.c | 2 +-
fs/f2fs/node.c | 18 ++++++++----------
fs/f2fs/shrinker.c | 2 +-
fs/f2fs/super.c | 7 ++++---
fs/f2fs/xattr.c | 3 ---
12 files changed, 107 insertions(+), 94 deletions(-)
next reply other threads:[~2020-03-11 16:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 16:27 Jaegeuk Kim [this message]
2020-03-11 17:20 ` Linus Torvalds
2020-03-11 17:20 ` Linus Torvalds
2020-03-11 17:35 ` Jaegeuk Kim
2020-03-11 17:41 ` Linus Torvalds
2020-03-11 17:48 ` Jaegeuk Kim
2020-04-07 21:05 ` 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=20200311162735.GA152176@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