1. 09 5月, 2007 1 次提交
  2. 26 4月, 2007 1 次提交
  3. 10 2月, 2007 1 次提交
  4. 18 1月, 2007 1 次提交
    • D
      JFS: call io_schedule() instead of schedule() to avoid deadlock · 4aa0d230
      Dave Kleikamp 提交于
      The introduction of Jens Axboe's explicit i/o plugging patches introduced a
      deadlock in jfs.  This was caused by the process initiating I/O not
      unplugging the queue before waiting on the commit thread.  The commit
      thread itself was waiting for that I/O to complete.  Calling io_schedule()
      rather than schedule() unplugs the I/O queue avoiding the deadlock, and it
      appears to be the right function to call in any case.
      Signed-off-by: NDave Kleikamp <shaggy@austin.ibm.com>
      4aa0d230
  5. 08 12月, 2006 1 次提交
  6. 02 10月, 2006 2 次提交
  7. 01 10月, 2006 1 次提交
  8. 27 9月, 2006 1 次提交
  9. 01 7月, 2006 1 次提交
  10. 05 6月, 2006 1 次提交
  11. 16 2月, 2006 1 次提交
  12. 25 1月, 2006 1 次提交
  13. 09 1月, 2006 1 次提交
    • O
      [PATCH] Fix and add EXPORT_SYMBOL(filemap_write_and_wait) · 28fd1298
      OGAWA Hirofumi 提交于
      This patch add EXPORT_SYMBOL(filemap_write_and_wait) and use it.
      
      See mm/filemap.c:
      
      And changes the filemap_write_and_wait() and filemap_write_and_wait_range().
      
      Current filemap_write_and_wait() doesn't wait if filemap_fdatawrite()
      returns error.  However, even if filemap_fdatawrite() returned an
      error, it may have submitted the partially data pages to the device.
      (e.g. in the case of -ENOSPC)
      
      <quotation>
      Andrew Morton writes,
      
      If filemap_fdatawrite() returns an error, this might be due to some
      I/O problem: dead disk, unplugged cable, etc.  Given the generally
      crappy quality of the kernel's handling of such exceptions, there's a
      good chance that the filemap_fdatawait() will get stuck in D state
      forever.
      </quotation>
      
      So, this patch doesn't wait if filemap_fdatawrite() returns the -EIO.
      
      Trond, could you please review the nfs part?  Especially I'm not sure,
      nfs must use the "filemap_fdatawrite(inode->i_mapping) == 0", or not.
      Acked-by: NTrond Myklebust <trond.myklebust@fys.uio.no>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      28fd1298
  14. 04 10月, 2005 1 次提交
    • D
      JFS: make special inodes play nicely with page balancing · ac17b8b5
      Dave Kleikamp 提交于
      This patch fixes up a few problems with jfs's reserved inodes.
      
      1. There is no need for the jfs code setting the I_DIRTY bits in i_state.
         I am ashamed that the code ever did this, and surprised it hasn't been
         noticed until now.
      
      2. Make sure special inodes are on an inode hash list.  If the inodes are
         unhashed, __mark_inode_dirty will fail to put the inode on the
         superblock's dirty list, and the data will not be flushed under memory
         pressure.
      
      3. Force writing journal data to disk when metapage_writepage is unable to
         write a metadata page due to pending journal I/O.
      Signed-off-by: NDave Kleikamp <shaggy@austin.ibm.com>
      ac17b8b5
  15. 21 9月, 2005 1 次提交
  16. 16 9月, 2005 1 次提交
  17. 11 8月, 2005 1 次提交
  18. 27 7月, 2005 1 次提交
    • D
      JFS: Improve sync barrier processing · cbc3d65e
      Dave Kleikamp 提交于
      Under heavy load, hot metadata pages are often locked by non-committed
      transactions, making them difficult to flush to disk.  This prevents
      the sync point from advancing past a transaction that had modified the
      page.
      
      There is a point during the sync barrier processing where all
      outstanding transactions have been committed to disk, but no new
      transaction have been allowed to proceed.  This is the best time
      to write the metadata.
      Signed-off-by: NDave Kleikamp <shaggy@austin.ibm.com>
      cbc3d65e
  19. 26 6月, 2005 1 次提交
    • C
      [PATCH] Cleanup patch for process freezing · 3e1d1d28
      Christoph Lameter 提交于
      1. Establish a simple API for process freezing defined in linux/include/sched.h:
      
         frozen(process)		Check for frozen process
         freezing(process)		Check if a process is being frozen
         freeze(process)		Tell a process to freeze (go to refrigerator)
         thaw_process(process)	Restart process
         frozen_process(process)	Process is frozen now
      
      2. Remove all references to PF_FREEZE and PF_FROZEN from all
         kernel sources except sched.h
      
      3. Fix numerous locations where try_to_freeze is manually done by a driver
      
      4. Remove the argument that is no longer necessary from two function calls.
      
      5. Some whitespace cleanup
      
      6. Clear potential race in refrigerator (provides an open window of PF_FREEZE
         cleared before setting PF_FROZEN, recalc_sigpending does not check
         PF_FROZEN).
      
      This patch does not address the problem of freeze_processes() violating the rule
      that a task may only modify its own flags by setting PF_FREEZE. This is not clean
      in an SMP environment. freeze(process) is therefore not SMP safe!
      Signed-off-by: NChristoph Lameter <christoph@lameter.com>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      3e1d1d28
  20. 05 5月, 2005 1 次提交
  21. 03 5月, 2005 3 次提交
  22. 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