1. 17 Nov, 2003 3 commits
    • David S. Miller's avatar
      Merge nuts.ninka.net:/disk1/davem/BK/network-2.5 · e92b29bc
      David S. Miller authored
      into nuts.ninka.net:/disk1/davem/BK/net-2.5
      e92b29bc
    • Jesse Barnes's avatar
      [PATCH] Fix bootmem breakage on ARM · f2b4a98e
      Jesse Barnes authored
      Russell King reports:
       "With previous kernels, the nodes are added to the list in reverse order,
        so architecture code knew we had to add the highest PFN first and the
        lowest PFN node last.
      
        Unfortunately, init_bootmem_core() now sorts the nodes according to
        their start pfn. This active sorting broke ARM discontig memory support."
      
      Andrew Morton chimes in:
       "It looks to be bogus on ia64 as well, for which the patch was written"
      
      Yep, I think it is bogus.  There's only one caller on ia64 that would be
      affected--swiotlb_init(), and afaik multi-node systems won't be using
      that code (except maybe NEC?), so even if the pgdat list is out of order
      we should be ok.  If not I'll fix the ia64 discontig code.
      f2b4a98e
    • Herbert Xu's avatar
      [PATCH] Fix double module_put in lockd · ea8d7db9
      Herbert Xu authored
      kernel_thread() returns the pid if successful, so the test for
      errors is to test for _negative_ values.
      ea8d7db9
  2. 16 Nov, 2003 3 commits
  3. 15 Nov, 2003 4 commits
  4. 14 Nov, 2003 2 commits
    • Paul Mackerras's avatar
      [PATCH] PPC32: cancel syscall restart on signal delivery · 6ebed0fa
      Paul Mackerras authored
      This patch ensures that the PPC kernel cancels any pending restarted
      system call when it delivers a signal.  This is the PPC counterpart of
      the change that has recently gone into i386 and other architectures.
      6ebed0fa
    • Paul Mackerras's avatar
      [PATCH] PPC32: Don't oops on out-of-range system call · 0837a685
      Paul Mackerras authored
      This patch fixes a bug on PPC where the kernel will oops if a process
      does a system call and the system call number is out of range.
      
      While fixing that, I noticed that if the process is being ptraced, an
      out-of-range system call will not get traced on the way in but will on
      the way out.  This patch fixes that too, by making it get traced on
      the way in as well as the way out.  It turned out to be less change,
      and fewer instructions overall, to do that than to make the
      out-of-range system call not be traced at all.
      0837a685
  5. 13 Nov, 2003 9 commits
  6. 12 Nov, 2003 9 commits
  7. 11 Nov, 2003 10 commits