1. 28 May, 2005 21 commits
  2. 27 May, 2005 10 commits
    • Linus Torvalds's avatar
    • Alexander Nyberg's avatar
      [PATCH] Note on ACPI build fix · 8aadff7d
      Alexander Nyberg authored
      Even after the previous fix you can still set CONFIG_ACPI_BOOT
      indirectly even without CONFIG_ACPI by choosing CONFIG_PCI and
      That doesn't build very well either.
      This makes PCI_MMCONFIG depend on ACPI, fixing that hole.
      [ I guess in theory Kconfig could follow the whole chain of dependencies
        for things that get selected, but that sounds insanely complicated, so
        we'll just fix up these things by hand.  --Linus ]
      Signed-off-by: default avatarAlexander Nyberg <alexn@telia.com>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
    • Len Brown's avatar
      [PATCH] ACPI build fix · 3e11c3ce
      Len Brown authored
      Fix 2.6.12 CONFIG_ACPI=n build regression.
      CONFIG_ACPI_BOOT shall be set only if CONFIG_ACPI.
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
    • Alexander Nyberg's avatar
      [PATCH] Fixup VIA IRQ quirk · 9920e914
      Alexander Nyberg authored
      quirk_via_irqpic can't be __devinit for swsuspend
      Signed-off-by: default avatarAlexander Nyberg <alexn@telia.com>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
    • Len Brown's avatar
      [PATCH] VIA IRQ quirk · 25be5e6c
      Len Brown authored
      Delete quirk_via_bridge(), restore quirk_via_irqpic() -- but now
      improved to be invoked upon device ENABLE, and now only for VIA devices
      -- not all devices behind VIA bridges.
      Signed-off-by: default avatarBjorn Helgaas <bjorn.helgaas@hp.com>
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
    • Paul Jackson's avatar
      [PATCH] cpuset exit NULL dereference fix · 2efe86b8
      Paul Jackson authored
      There is a race in the kernel cpuset code, between the code
      to handle notify_on_release, and the code to remove a cpuset.
      The notify_on_release code can end up trying to access a
      cpuset that has been removed.  In the most common case, this
      causes a NULL pointer dereference from the routine cpuset_path.
      However all manner of bad things are possible, in theory at least.
      The existing code decrements the cpuset use count, and if the
      count goes to zero, processes the notify_on_release request,
      if appropriate.  However, once the count goes to zero, unless we
      are holding the global cpuset_sem semaphore, there is nothing to
      stop another task from immediately removing the cpuset entirely,
      and recycling its memory.
      The obvious fix would be to always hold the cpuset_sem
      semaphore while decrementing the use count and dealing with
      notify_on_release.  However we don't want to force a global
      semaphore into the mainline task exit path, as that might create
      a scaling problem.
      The actual fix is almost as easy - since this is only an issue
      for cpusets using notify_on_release, which the top level big
      cpusets don't normally need to use, only take the cpuset_sem
      for cpusets using notify_on_release.
      This code has been run for hours without a hiccup, while running
      a cpuset create/destroy stress test that could crash the existing
      kernel in seconds.  This patch applies to the current -linus
      git kernel.
      Signed-off-by: default avatarPaul Jackson <pj@sgi.com>
      Acked-by: default avatarSimon Derr <simon.derr@bull.net>
      Acked-by: default avatarDinakar Guniguntala <dino@in.ibm.com>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
    • Alan Cox's avatar
      [PATCH] remove non-cleanroom pwc driver compression · 88c18346
      Alan Cox authored
      The original pwc author raised some questions about the reverse
      engineering of the decompressor algorithms used in the pwc driver.
      Having done some detailed investigation it appears those concerns that
      clean room policy was not followed are reasonable.  I've also had a
      friendly discussion with Philips to ask their view on this.
      This removes the problem items of code which reduces the pwc
      functionality in the kernel a little but leaves all the framework for
      setup that will be needed for decompressors in user space (where they
      eventually belong).  This change set is designed to be the minimal risk
      change set given that 2.6.12 is hopefully close to hand, with a view to
      merging the much updated pwc code in 2.6.13 series kernels.
      Someone else can then redo the decompressors properly (clean room) in
      user space.
      Note that while its easy to say that it should have been caught earlier,
      but the violation was really only obvious to someone who had access to
      both the proprietary source and the 'GPL' source.
    • Linus Torvalds's avatar
      ide-cd: revert DMA mask test change · 5d9e4ea5
      Linus Torvalds authored
      The change to require the DMA length to be only word-aligned was not
    • Christoph Hellwig's avatar
      [XFS] remove an over-zealous WARN_ON · 66f55071
      Christoph Hellwig authored
    • Christoph Hellwig's avatar
  3. 26 May, 2005 9 commits