1. 26 6月, 2015 9 次提交
  2. 25 6月, 2015 21 次提交
  3. 19 6月, 2015 1 次提交
    • P
      seqcount: Rename write_seqcount_barrier() · a7c6f571
      Peter Zijlstra 提交于
      I'll shortly be introducing another seqcount primitive that's useful
      to provide ordering semantics and would like to use the
      write_seqcount_barrier() name for that.
      
      Seeing how there's only one user of the current primitive, lets rename
      it to invalidate, as that appears what its doing.
      
      While there, employ lockdep_assert_held() instead of
      assert_spin_locked() to not generate debug code for regular kernels.
      Signed-off-by: NPeter Zijlstra (Intel) <peterz@infradead.org>
      Cc: ktkhai@parallels.com
      Cc: rostedt@goodmis.org
      Cc: juri.lelli@gmail.com
      Cc: pang.xunlei@linaro.org
      Cc: Oleg Nesterov <oleg@redhat.com>
      Cc: wanpeng.li@linux.intel.com
      Cc: Paul McKenney <paulmck@linux.vnet.ibm.com>
      Cc: Al Viro <viro@ZenIV.linux.org.uk>
      Cc: Linus Torvalds <torvalds@linux-foundation.org>
      Cc: umgwanakikbuti@gmail.com
      Link: http://lkml.kernel.org/r/20150611124743.279926217@infradead.orgSigned-off-by: NThomas Gleixner <tglx@linutronix.de>
      a7c6f571
  4. 12 6月, 2015 3 次提交
  5. 10 6月, 2015 1 次提交
  6. 09 6月, 2015 2 次提交
  7. 03 6月, 2015 3 次提交
    • J
      f2fs: fix to return exact trimmed size · f56aa1c5
      Jaegeuk Kim 提交于
      Now, we add all the candidates for trim commands and then finally issue
      discard commands.
      So, we should count the trimmed size in back-end.
      Signed-off-by: NJaegeuk Kim <jaegeuk@kernel.org>
      f56aa1c5
    • S
      vfs: read file_handle only once in handle_to_path · 161f873b
      Sasha Levin 提交于
      We used to read file_handle twice.  Once to get the amount of extra
      bytes, and once to fetch the entire structure.
      
      This may be problematic since we do size verifications only after the
      first read, so if the number of extra bytes changes in userspace between
      the first and second calls, we'll have an incoherent view of
      file_handle.
      
      Instead, read the constant size once, and copy that over to the final
      structure without having to re-read it again.
      Signed-off-by: NSasha Levin <sasha.levin@oracle.com>
      Cc: Al Viro <viro@zeniv.linux.org.uk>
      Cc: stable@vger.kernel.org
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      161f873b
    • C
      f2fs: support FALLOC_FL_INSERT_RANGE · f62185d0
      Chao Yu 提交于
      FALLOC_FL_INSERT_RANGE flag for ->fallocate was introduced in commit
      dd46c787 ("fs: Add support FALLOC_FL_INSERT_RANGE for fallocate").
      
      The effect of FALLOC_FL_INSERT_RANGE command is the opposite of
      FALLOC_FL_COLLAPSE_RANGE, if this command was performed, all data from
      offset to EOF in our file will be shifted to right as given length, and
      then range [offset, offset + length] becomes a hole.
      
      This command is useful for our user who wants to add some data in the
      middle of the file, for example: video/music editor will insert a keyframe
      in specified position of media file, with this command we can easily create
      a hole for inserting without removing original data.
      
      This patch introduces f2fs_insert_range() to support FALLOC_FL_INSERT_RANGE.
      Signed-off-by: NChao Yu <chao2.yu@samsung.com>
      Signed-off-by: NYuan Zhong <yuan.mark.zhong@samsung.com>
      Signed-off-by: NJaegeuk Kim <jaegeuk@kernel.org>
      f62185d0