1. 29 1月, 2008 11 次提交
  2. 18 10月, 2007 3 次提交
  3. 01 8月, 2007 1 次提交
    • M
      "ext4_ext_put_in_cache" uses __u32 to receive physical block number · dd54567a
      Mingming Cao 提交于
      Yan Zheng wrote:
      
      > I think I found a bug in ext4/extents.c, "ext4_ext_put_in_cache" uses
      > "__u32" to receive physical block number.  "ext4_ext_put_in_cache" is
      > used in "ext4_ext_get_blocks", it sets ext4 inode's extent cache
      > according most recently tree lookup (higher 16 bits of saved physical
      > block number are always zero). when serving a mapping request,
      > "ext4_ext_get_blocks" first check whether the logical block is in
      > inode's extent cache. if the logical block is in the cache and the
      > cached region isn't a gap, "ext4_ext_get_blocks" gets physical block
      > number by using cached region's physical block number and offset in
      > the cached region.  as described above, "ext4_ext_get_blocks" may
      > return wrong result when there are physical block numbers bigger than
      > 0xffffffff.
      >
      
      You are right.  Thanks for reporting this!
      Signed-off-by: NMingming Cao <cmm@us.ibm.com>
      Cc: Yan Zheng <yanzheng@21cn.com>
      Cc: <stable@kernel.org>
      Cc: <linux-ext4@vger.kernel.org>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      dd54567a
  4. 18 7月, 2007 6 次提交
  5. 01 6月, 2007 4 次提交
  6. 09 5月, 2007 1 次提交
  7. 18 2月, 2007 1 次提交
  8. 08 12月, 2006 5 次提交
  9. 12 10月, 2006 7 次提交