1. 01 8月, 2006 1 次提交
  2. 01 7月, 2006 1 次提交
  3. 27 6月, 2006 1 次提交
  4. 27 3月, 2006 1 次提交
  5. 23 3月, 2006 1 次提交
  6. 19 3月, 2006 1 次提交
  7. 21 2月, 2006 5 次提交
  8. 15 2月, 2006 4 次提交
  9. 06 2月, 2006 3 次提交
  10. 15 1月, 2006 1 次提交
  11. 09 1月, 2006 1 次提交
  12. 14 11月, 2005 1 次提交
  13. 09 11月, 2005 1 次提交
  14. 09 10月, 2005 1 次提交
  15. 13 9月, 2005 5 次提交
  16. 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
  17. 24 6月, 2005 1 次提交
  18. 21 5月, 2005 1 次提交
  19. 17 5月, 2005 2 次提交
    • P
      [PATCH] CDRW/DVD packet writing data corruption fix · 7baeb6a5
      Peter Osterlund 提交于
      I found a bug in the packet writing driver that could cause data
      corruption.  The problem arised if the driver got a write request for a
      sector in a "zone" it was already working on.  In that case it was supposed
      to queue the write request until it was done processing earlier requests
      for the same zone, and instead work on some other zone in the mean time.
      However, if there was no other zone to work on, the driver would initiate
      two packet_data objects for the same zone, causing unpredictable things to
      happen.
      Signed-off-by: NPeter Osterlund <petero2@telia.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      7baeb6a5
    • P
      [PATCH] Fix root hole in pktcdvd · 118326e9
      Peter Osterlund 提交于
      ioctl_by_bdev may only be used INSIDE the kernel.  If the "arg" argument
      refers to memory that is accessed by put_user/get_user in the ioctl
      function, the memory needs to be in the kernel address space (that's the
      set_fs(KERNEL_DS) doing in the ioctl_by_bdev).  This works on i386 because
      even with set_fs(KERNEL_DS) the user space memory is still accessible with
      put_user/get_user.  That is not true for s390.  In short the ioctl
      implementation of the pktcdvd device driver is horribly broken.
      Signed-off-by: NPeter Osterlund <petero2@telia.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      118326e9
  20. 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