1. 02 6月, 2015 1 次提交
  2. 29 5月, 2015 6 次提交
  3. 11 4月, 2015 6 次提交
  4. 04 3月, 2015 1 次提交
  5. 10 1月, 2015 1 次提交
  6. 24 11月, 2014 1 次提交
  7. 04 11月, 2014 10 次提交
  8. 16 9月, 2014 1 次提交
  9. 10 9月, 2014 1 次提交
  10. 04 9月, 2014 1 次提交
  11. 22 8月, 2014 1 次提交
  12. 20 8月, 2014 1 次提交
  13. 11 7月, 2014 1 次提交
    • C
      f2fs: check name_len of dir entry to prevent from deadloop · 81e366f8
      Chao Yu 提交于
      We assume that modification of some special application could result in zeroed
      name_len, or it is consciously made by somebody. We will deadloop in
      find_in_block when name_len of dir entry is zero.
      
      This patch is added for preventing deadloop in above scenario.
      
      change log from v1:
       o use f2fs_bug_on rather than break out from searching dir entry suggested by
      Jaegeuk Kim.
      
      Jaegeuk describe:
      "Well, IMO, it would be good to add f2fs_bug_on() here with a specific comment.
      In the current phase of f2fs, it is more important to investigate the file
      system bugs, rather than workarounds for any corrupted images.
      And, definitely it needs to stop the kernel if any corrupted image was mounted,
      so that we can figure out where the bugs are occurred."
      Suggested-by: NJaegeuk Kim <jaegeuk@kernel.org>
      Signed-off-by: NChao Yu <chao2.yu@samsung.com>
      Signed-off-by: NJaegeuk Kim <jaegeuk@kernel.org>
      81e366f8
  14. 10 7月, 2014 5 次提交
  15. 09 7月, 2014 1 次提交
    • C
      f2fs: fix error path in init_inode_metadata · 90d72459
      Chao Yu 提交于
      If we fail in this path:
      ->init_inode_metadata
        ->make_empty_dir
          ->get_new_data_page
            ->grab_cache_page return -ENOMEM
      
      We will bug on in error path of init_inode_metadata when call remove_inode_page
      because i_block = 2 (one inode block will be released later & one dentry block).
      
      We should release the dentry block in init_inode_metadata to avoid this BUG_ON,
      and avoid leak of dentry block resource, because we never have second chance to
      release that block in ->evict_inode as in upper error path we make this inode
      'bad'.
      Signed-off-by: NChao Yu <chao2.yu@samsung.com>
      Signed-off-by: NJaegeuk Kim <jaegeuk@kernel.org>
      90d72459
  16. 04 6月, 2014 1 次提交
  17. 07 5月, 2014 1 次提交