1. 17 Apr, 2003 2 commits
  2. 16 Apr, 2003 7 commits
  3. 15 Apr, 2003 12 commits
    • Jan Harkes's avatar
      [PATCH] Fix coda/devfs oops · c78e8101
      Jan Harkes authored
      The problem is caused by the devfs_mk_dir simplification that went in a
      couple of weeks ago that didn't update one of the coda call-sites.
      c78e8101
    • David Mosberger's avatar
      [PATCH] module symbol fix · f5d27787
      David Mosberger authored
      Fix for trivial typo.  Without it, you can't insert anything on top of
      agpgart.ko because the agp_register_driver() will erroneously pick up
      the symbol version from agp_backend_acquire().
      f5d27787
    • George Anzinger's avatar
      [PATCH] Cleanups for posix timer hang fix · 18550640
      George Anzinger authored
      Clean up "pendcount" locking (or rather - lack there-of) by making it a
      per-timer thing and thus automatically protected by the timer lock.
      
      Fix whitespace damage.
      18550640
    • Linus Torvalds's avatar
      Merge bk://are.twiddle.net/axp-2.5 · a0b2fc70
      Linus Torvalds authored
      into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux
      a0b2fc70
    • Richard Henderson's avatar
    • Ulrich Drepper's avatar
      [PATCH] unwinding for vsyscall code · e60ef815
      Ulrich Drepper authored
      Now that the kernel provides code user programs are executing directly
      (I mean the vsyscall code on x86) it is necessary to add unwind
      information for that code as well.  The unwind information is used not
      only in C++ code.
      
      This patch adds a AT_SYSINFO_EH_FRAME ELF aux-table value that points to
      the unwinding block description for the sysinfo frame, and makes sure
      the AT_* value is passed to applications.  It defines the static data
      for the unwind blocks (two, one for int80 and the other for sysenter),
      and finally adds code to copy the data in place.
      e60ef815
    • Linus Torvalds's avatar
      Fix typo (and logic bug that the typo hid) in bit value · 30485186
      Linus Torvalds authored
      testing. 
      
      Found by 'sparse', my source parser tool.
      30485186
    • Matt Reppert's avatar
      [ALPHA] Include module.h for EXPORT_SYMBOL. · a3b4f7f1
      Matt Reppert authored
      a3b4f7f1
    • Ivan Kokshaysky's avatar
      [PATCH] alpha: lynx support · b94ce25b
      Ivan Kokshaysky authored
      Forward port of Jay's 2.4 patch.
      Also I've cleaned up EISA configury - we only need it for
      systems with EISA.
      
      Ivan.
      b94ce25b
    • Ivan Kokshaysky's avatar
      [PATCH] alpha: move_initrd fix (from Jeff Wiedemeier) · d33a9219
      Ivan Kokshaysky authored
      While testing our upcoming kernel update for 7.2 alpha, I've encountered
      a problem with move_initrd. It allocates a page-aligned chunk to move
      the initrd into, but it doesn't allocate the entire last
      page. Subsequent bootmem allocations can then be filled from the last
      page used be the initrd.  This then becomes a problem when the initrd
      memory is released.
      d33a9219
    • Ivan Kokshaysky's avatar
      [PATCH] alpha: execve() fix · 9a357b21
      Ivan Kokshaysky authored
      The 2.5 kernels may hang on execve(). Most easily this can be reproduced
      by submitting forms in mozilla, apparently because it does execve with
      very long argument strings.
      That's what happens in do_execve, I suppose:
      	bprm.mm = mm_alloc();
      	...
      	init_new_context(current, bprm.mm); here we update current ptbr
      					    with new mm->pgd
      	...
      	copy_strings;
      			interrupt -> do_softirq -> switch to ksoftirqd
      			...
      			switch back to do_execve;
      	copy_strings -  immediate page fault in copy_user that we can't
      			handle because the new ptbr has been activated
      			after context switch and current->mm is not
      			valid anymore.
      
      The fix is to not update ptbr for current task in init_new_context(),
      as we do it later in activate_mm() anyway.
      
      With it my (UP) boxes look quite stable so far.
      
      Ivan.
      9a357b21
    • Richard Henderson's avatar
      Merge are.twiddle.net:/home/rth/BK/linus-2.5 · cacc230d
      Richard Henderson authored
      into are.twiddle.net:/home/rth/BK/axp-2.5
      cacc230d
  4. 14 Apr, 2003 19 commits
    • Randolph Chung's avatar
      [PATCH] {get,set}affinity unification · 693ccaab
      Randolph Chung authored
      This one gets rid of sys32_{get,set}affinity in favor of a unified
      compat implementation.
      693ccaab
    • Greg Kroah-Hartman's avatar
    • Greg Kroah-Hartman's avatar
    • Andrew Morton's avatar
      [PATCH] Resource management for NFS... · 8a9e7331
      Andrew Morton authored
      From: Trond Myklebust <trond.myklebust@fys.uio.no>
      
      The patch fixes some problems with NFS under heavy writeout.
      
      NFS pages can be in a clean but unreclaimable state.  They are unreclaimable
      because the server has not yet acked the write - we may need to "redirty"
      them if the server crashes.
      
      These are referred to as "unstable" pages.  We need to count them alongside
      dirty and writeback pages when making flushing and throttling decisions.
      Otherwise the machine can be flooded with these pages and the VM has
      problems.
      8a9e7331
    • Andrew Morton's avatar
      [PATCH] fix MCE startup ordering problems · 95751430
      Andrew Morton authored
      The MCE code is setting up a timer whose handler uses the workqueue code
      before workqueue is initialised.  If you boot slowly it oopses.
      
      Convert the MCE code to use an initcall.
      95751430
    • Andrew Morton's avatar
      [PATCH] Posix timer hang fix · cffa97e1
      Andrew Morton authored
      From: george anzinger <george@mvista.com>
      
      The MAJOR problem was a hang in the kernel if a user tried to delete a
      repeating timer that had a signal delivery pending. I was putting the
      task in a loop waiting for that same task to pick up the signal. OUCH!
      
      A minor issue relates to the need by the glibc folks, to specify a
      particular thread to get the signal.  I had this code in all along,
      but somewhere in 2.5 the signal code was made POSIX compliant, i.e.
      deliver to the first thread that doesn't have it masked out.
      
      This now uses the code from the above mentioned clean up.  Most
      signals go to the group delivery signal code, however, those
      specifying THREAD_ID (an extension to the POSIX standard) are sent to
      the specified thread.  That thread MUST be in the same thread group as
      the thread that creates the timer.
      cffa97e1
    • Andrew Morton's avatar
      [PATCH] export kernel_fpu_begin() to GPL modules · ba411795
      Andrew Morton authored
      drivers/md/xor.c needs kernel_fpu_begin() for the mmx checksumming functions.
       So export that to GPL modules.
      ba411795
    • Andrew Morton's avatar
      [PATCH] genrtc: jiffies type fix · 228be800
      Andrew Morton authored
      use `unsigned long' for a jiffies-holding type.
      228be800
    • Andrew Morton's avatar
      [PATCH] fix tty shutdown race · 59b6573c
      Andrew Morton authored
      use-after-free races have been seen due to the workqueue timer in the tty
      structure going off after the tty was freed.
      
      Fix that up by using cancel_scheduled_work() and flush_scheduled_work().
      59b6573c
    • Andrew Morton's avatar
      [PATCH] flush_work_queue() fixes · 92b817f8
      Andrew Morton authored
      The workqueue code currently has a notion of a per-cpu queue being "busy".
      flush_scheduled_work()'s responsibility is to wait for a queue to be not busy.
      
      Problem is, flush_scheduled_work() can easily hang up.
      
      - The workqueue is deemed "busy" when there are pending delayed
        (timer-based) works.  But if someone repeatedly schedules new delayed work
        in the callback, the queue will never fall idle, and flush_scheduled_work()
        will not terminate.
      
      - If someone reschedules work (not delayed work) in the work function, that
        too will cause the queue to never go idle, and flush_scheduled_work() will
        not terminate.
      
      So what this patch does is:
      
      - Create a new "cancel_delayed_work()" which will try to kill off any
        timer-based delayed works.
      
      - Change flush_scheduled_work() so that it is immune to people re-adding
        work in the work callout handler.
      
        We can do this by recognising that the caller does *not* want to wait
        until the workqueue is "empty".  The caller merely wants to wait until all
        works which were pending at the time flush_scheduled_work() was called have
        completed.
      
        The patch uses a couple of sequence numbers for that.
      
      So now, if someone wants to reliably remove delayed work they should do:
      
      
      	/*
      	 * Make sure that my work-callback will no longer schedule new work
      	 */
      	my_driver_is_shutting_down = 1;
      
      	/*
      	 * Kill off any pending delayed work
      	 */
      	cancel_delayed_work(&my_work);
      
      	/*
      	 * OK, there will be no new works scheduled.  But there may be one
      	 * currently queued or in progress.  So wait for that to complete.
      	 */
      	flush_scheduled_work();
      
      
      The patch also changes the flush_workqueue() sleep to be uninterruptible.
      We cannot legally bale out if a signal is delivered anyway.
      92b817f8
    • Andrew Morton's avatar
      [PATCH] Fix oprofile on hyperthreaded P4's · ec7708a2
      Andrew Morton authored
      From: Philippe Elie <phil.el@wanadoo.fr>
      
      - oprofile is currently only profiling one sibling.  Fix that with
        appropriate register settings.
      
      - fix an oops which could occur if the userspace driver were to request a
        non-existent resource.
      
      - in NMI handler counter_config[i].event is accessible from user space so
        user can change the event during profiling by echo xxx >
        /dev/oprofile/event
      
      - event mask was wrong, the bit field is 6 bits length not 5, events
        SSE_INPUT_ASSIST and X87_SIMD_MOVES_UOP was affected by masking high bit of
        event number.
      ec7708a2
    • Andrew Morton's avatar
      [PATCH] missing file_lock conversions · 4e09bf0b
      Andrew Morton authored
      A few places were missing the rwlock->spinlock conversion.
      4e09bf0b
    • Linus Torvalds's avatar
    • Linus Torvalds's avatar
      Make the x86 flags save/restore code check the type of the · 81da5c11
      Linus Torvalds authored
      macro argument, so that portability issues will be found in
      a timely manner.
      81da5c11
    • Greg Kroah-Hartman's avatar
      [PATCH] Input: change input_init() to be a subsys initcall · 44d3f356
      Greg Kroah-Hartman authored
      This fixes oopses when it and the hid core are compiled into the kernel.
      44d3f356
    • Ben Collins's avatar
      [PATCH] Fix nodemgr.c compile · 57cf0f92
      Ben Collins authored
      57cf0f92
    • Arnaldo Carvalho de Melo's avatar
    • Geert Uytterhoeven's avatar
      [PATCH] Amiga Gayle IDE fixes · df27e778
      Geert Uytterhoeven authored
      Amiga Gayle IDE fixes: Set hwif->mmio to 2 to prevent the generic IDE core from
      messing with our resources
      df27e778
    • Geert Uytterhoeven's avatar
      [PATCH] Amiga keyboard updates · fdff3db6
      Geert Uytterhoeven authored
      Amiga keyboard: fix default keyboard mappings:
        - Map the parentheses keys on the numeric keypad to KPLEFTPAREN and
          KPRIGHTPAREN (was: NUMLOCK and SCROLLLOCK)
        - Map the Help key to HELP (was: F11)
        - Map the Amiga keys to LEFTMETA and RIGHTMETA (was: RESERVED)
      fdff3db6