1. 20 6月, 2005 3 次提交
  2. 21 5月, 2005 1 次提交
  3. 17 4月, 2005 4 次提交
    • [PATCH] fix NMI lockup with CFQ scheduler · 152587de
      提交于
      The current problem seen is that the queue lock is actually in the
      SCSI device structure, so when that structure is freed on device
      release, we go boom if the queue tries to access the lock again.
      
      The fix here is to move the lock from the scsi_device to the queue.
      Signed-off-by: NJames Bottomley <James.Bottomley@SteelEye.com>
      152587de
    • K
      [PATCH] use cheaper elv_queue_empty when unplug a device · a2997382
      Ken Chen 提交于
      In function __generic_unplug_device(), kernel can use a cheaper function
      elv_queue_empty() instead of more expensive elv_next_request to find
      whether the queue is empty or not.  blk_run_queue can also made conditional
      on whether queue's emptiness before calling request_fn().
      Signed-off-by: NJens Axboe <axboe@suse.de>
      Signed-off-by: NKen Chen <kenneth.w.chen@intel.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      a2997382
    • J
      [PATCH] possible use-after-free of bio · 4a534f93
      Jens Axboe 提交于
      There is a possibility that a bio will be accessed after it has been freed
      on SCSI.  It happens if you submit a bio with BIO_SYNC marked and the
      auto-unplugging kicks the request_fn, SCSI re-enables interrupts in-between
      so if the request completes between the add_request() in __make_request()
      and the bio_sync() call, we could be looking at a dead bio.  It's a slim
      race, but it has been triggered in the Real World.
      
      So assign bio_sync() to a local variable instead.
      Signed-off-by: NJens Axboe <axboe@suse.de>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      4a534f93
    • 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