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 bug fix for 4.8-rc4
Date: Tue, 23 Aug 2016 16:35:03 -0700 [thread overview]
Message-ID: <20160823233503.GA78328@jaegeuk> (raw)
Hi Linus,
Could you consider this pull request?
Thanks,
The following changes since commit 3408fef7448ce7d3c926978ee1a511e7707bffba:
Merge branch 'x86-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip (2016-08-18 15:09:41 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git tags/for-f2fs-v4.8-rc4
for you to fetch changes up to 20a3d61d46e1fb45efa6eb4637c0dcd3f00a14e9:
f2fs: avoid potential deadlock in f2fs_move_file_range (2016-08-19 11:15:08 +0900)
----------------------------------------------------------------
Bug/regression fix
- fsmark regression
- i_size race condition
- wrong conditions in f2fs_move_file_range
----------------------------------------------------------------
Chao Yu (3):
Revert "f2fs: move i_size_write in f2fs_write_end"
f2fs: allow copying file range only in between regular files
f2fs: avoid potential deadlock in f2fs_move_file_range
Jaegeuk Kim (1):
Revert "f2fs: use percpu_rw_semaphore"
fs/f2fs/data.c | 2 +-
fs/f2fs/f2fs.h | 12 ++++++------
fs/f2fs/file.c | 13 +++++++++----
fs/f2fs/node.c | 47 +++++++++++++++++++++++------------------------
fs/f2fs/super.c | 6 +-----
5 files changed, 40 insertions(+), 40 deletions(-)
------------------------------------------------------------------------------
reply other threads:[~2016-08-23 23:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160823233503.GA78328@jaegeuk \
--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).