1. 30 9月, 2010 1 次提交
    • J
      ocfs2: Don't walk off the end of fast symlinks. · 1fc8a117
      Joel Becker 提交于
      ocfs2 fast symlinks are NUL terminated strings stored inline in the
      inode data area.  However, disk corruption or a local attacker could, in
      theory, remove that NUL.  Because we're using strlen() (my fault,
      introduced in a731d1 when removing vfs_follow_link()), we could walk off
      the end of that string.
      Signed-off-by: NJoel Becker <joel.becker@oracle.com>
      Cc: stable@kernel.org
      1fc8a117
  2. 12 1月, 2010 1 次提交
  3. 24 12月, 2009 1 次提交
  4. 24 9月, 2009 1 次提交
  5. 09 5月, 2009 1 次提交
  6. 06 1月, 2009 1 次提交
    • J
      ocfs2: Wrap inode block reads in a dedicated function. · b657c95c
      Joel Becker 提交于
      The ocfs2 code currently reads inodes off disk with a simple
      ocfs2_read_block() call.  Each place that does this has a different set
      of sanity checks it performs.  Some check only the signature.  A couple
      validate the block number (the block read vs di->i_blkno).  A couple
      others check for VALID_FL.  Only one place validates i_fs_generation.  A
      couple check nothing.  Even when an error is found, they don't all do
      the same thing.
      
      We wrap inode reading into ocfs2_read_inode_block().  This will validate
      all the above fields, going readonly if they are invalid (they never
      should be).  ocfs2_read_inode_block_full() is provided for the places
      that want to pass read_block flags.  Every caller is passing a struct
      inode with a valid ip_blkno, so we don't need a separate blkno argument
      either.
      
      We will remove the validation checks from the rest of the code in a
      later commit, as they are no longer necessary.
      Signed-off-by: NJoel Becker <joel.becker@oracle.com>
      Signed-off-by: NMark Fasheh <mfasheh@suse.com>
      b657c95c
  7. 15 10月, 2008 2 次提交
  8. 14 10月, 2008 2 次提交
  9. 01 5月, 2008 1 次提交
  10. 08 5月, 2007 1 次提交
  11. 13 2月, 2007 1 次提交
  12. 22 1月, 2007 1 次提交
  13. 02 12月, 2006 1 次提交
  14. 30 6月, 2006 1 次提交
  15. 23 6月, 2006 1 次提交
  16. 04 1月, 2006 1 次提交