1. 11 9月, 2005 1 次提交
  2. 08 9月, 2005 1 次提交
    • D
      [PATCH] fix cramfs making duplicate entries in inode cache · a97c9bf3
      Dave Johnson 提交于
      Every time cramfs_lookup() is called to lookup and inode for a dentry,
      get_cramfs_inode() will allocate a new inode without checking to see if that
      inode already exists in the inode cache.
      
      This is fine the first time, but if the dentry cache entry(ies) associated
      with that inode are aged out, but the inode entry is not aged out (which can
      be quite common if the inode has buffer cache linked to it), cramfs_lookup()
      will be called again and another inode will be allocated and added to the
      inode cache creating a duplicate in the inode cache.
      
      The big issue here is that the buffers associated with each inode cache entry
      are not shared between the duplicates!
      
      The older inode entries are now orphaned as no dentry points to it and won't
      be freed until the buffer cache assoicated with them are first freed.  The
      newest entry will have to create all new buffer cache for each part of its
      file as the old buffer cache is now orphaned as well.
      
      Patch below fixes this by making get_cramfs_inode() use the inode cache before
      blindly creating a new entry every time.  This eliminates the duplicate inodes
      and duplicate buffer cache.
      
      Cc: Phillip Lougher <phillip@lougher.demon.co.uk>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      a97c9bf3
  3. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4
反馈
建议
客服 返回
顶部