1. 29 Aug, 2005 1 commit
    • Steven Rostedt's avatar
      [PATCH] convert signal handling of NODEFER to act like other Unix boxes. · 69be8f18
      Steven Rostedt authored
      It has been reported that the way Linux handles NODEFER for signals is
      not consistent with the way other Unix boxes handle it.  I've written a
      program to test the behavior of how this flag affects signals and had
      several reports from people who ran this on various Unix boxes,
      confirming that Linux seems to be unique on the way this is handled.
      
      The way NODEFER affects signals on other Unix boxes is as follows:
      
      1) If NODEFER is set, other signals in sa_mask are still blocked.
      
      2) If NODEFER is set and the signal is in sa_mask, then the signal is
      still blocked. (Note: this is the behavior of all tested but Linux _and_
      NetBSD 2.0 *).
      
      The way NODEFER affects signals on Linux:
      
      1) If NODEFER is set, other signals are _not_ blocked regardless of
      sa_mask (Even NetBSD doesn't do this).
      
      2) If NODEFER is set and the signal is in sa_mask, then the signal being
      handled is not blocked.
      
      The patch converts signal handling in all current Linux architectures to
      the way most Unix boxes work.
      
      Unix boxes that were tested:  DU4, AIX 5.2, Irix 6.5, NetBSD 2.0, SFU
      3.5 on WinXP, AIX 5.3, Mac OSX, and of course Linux 2.6.13-rcX.
      
      * NetBSD was the only other Unix to behave like Linux on point #2. The
      main concern was brought up by point #1 which even NetBSD isn't like
      Linux.  So with this patch, we leave NetBSD as the lonely one that
      behaves differently here with #2.
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      69be8f18
  2. 28 Aug, 2005 5 commits
  3. 27 Aug, 2005 16 commits
  4. 26 Aug, 2005 15 commits
  5. 25 Aug, 2005 1 commit
    • Michael Chan's avatar
      [TG3]: Fix ethtool loopback test lockup · d4ef1608
      Michael Chan authored
      The tg3_abort_hw() call in tg3_test_loopback() is causing lockups on
      some devices. tg3_abort_hw() disables the memory arbiter, causing
      tg3_reset_hw() to hang when it tries to write the pre-reset signature.
      tg3_abort_hw() should only be called after the pre-reset signature has
      been written. This is all done in tg3_reset_hw() so the tg3_abort_hw()
      call is unnecessary and can be removed.
      
      [ Also bump driver version and release date. -DaveM ]
      Signed-off-by: default avatarMichael Chan <mchan@broadcom.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      d4ef1608
  6. 24 Aug, 2005 2 commits