1. 17 2月, 2007 3 次提交
  2. 04 10月, 2006 1 次提交
  3. 28 6月, 2006 1 次提交
  4. 23 6月, 2006 1 次提交
    • L
      [PATCH] fix incorrect SA_ONSTACK behaviour for 64-bit processes · d09042da
      Laurent MEYER 提交于
      - When setting a sighandler using sigaction() call, if the flag
        SA_ONSTACK is set and no alternate stack is provided via sigaltstack(),
        the kernel still try to install the alternate stack.  This behavior is
        the opposite of the one which is documented in Single Unix Specifications
        V3.
      
      - Also when setting an alternate stack using sigaltstack() with the flag
        SS_DISABLE, the kernel try to install the alternate stack on signal
        delivery.
      
      These two use cases makes the process crash at signal delivery.
      Signed-off-by: NLaurent Meyer <meyerlau@fr.ibm.com>
      Cc: Richard Henderson <rth@twiddle.net>
      Cc: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
      Cc: David Howells <dhowells@redhat.com>
      Cc: Yoshinori Sato <ysato@users.sourceforge.jp>
      Cc: Geert Uytterhoeven <geert@linux-m68k.org>
      Cc: Roman Zippel <zippel@linux-m68k.org>
      Cc: Kyle McMartin <kyle@mcmartin.ca>
      Cc: Paul Mundt <lethal@linux-sh.org>
      Cc: Kazumoto Kojima <kkojima@rr.iij4u.or.jp>
      Cc: Chris Zankel <chris@zankel.net>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      d09042da
  5. 23 1月, 2006 1 次提交
    • K
      [PARISC] Arch-specific compat signals · f671c45d
      Kyle McMartin 提交于
      Add enough arch-specific compat signals code to enable parisc64
      to compile and boot out of the mainline tree. There are likely still
      many dragons here, but this is a start to squashing the last
      big difference between the mainline tree and the parisc-linux tree.
      The remaining bugs can be squashed as they come up.
      Signed-off-by: NKyle McMartin <kyle@parisc-linux.org>
      f671c45d
  6. 18 11月, 2005 1 次提交
  7. 22 10月, 2005 3 次提交
  8. 10 9月, 2005 1 次提交
  9. 30 8月, 2005 1 次提交
    • S
      [PATCH] convert signal handling of NODEFER to act like other Unix boxes. · 69be8f18
      Steven Rostedt 提交于
      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: NLinus Torvalds <torvalds@osdl.org>
      69be8f18
  10. 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