1. 26 4月, 2007 1 次提交
  2. 13 4月, 2007 1 次提交
    • R
      [SPARC]: avoid CHILD_MAX and OPEN_MAX constants · 1d51c69f
      Roland McGrath 提交于
      I don't figure anyone really cares about SunOS syscall emulation, and I
      certainly don't.  But I'm getting rid of uses of the OPEN_MAX and CHILD_MAX
      compile-time constant, and these are almost the only ones.  OPEN_MAX is a
      bogus constant with no meaning about anything.  The RLIMIT_NOFILE resource
      limit is what sysconf (_SC_OPEN_MAX) actually wants to return.
      
      The CHILD_MAX cases weren't actually using anything I want to get rid of,
      but I noticed that they are there and are wrong too.  The CHILD_MAX value
      is not really unlimited as a -1 return from sysconf indicates.  The
      RLIMIT_NPROC resource limit is what sysconf (_SC_CHILD_MAX) wants to return.
      Signed-off-by: NRoland McGrath <roland@redhat.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      1d51c69f
  3. 09 12月, 2006 2 次提交
    • J
      [PATCH] struct path: convert sparc64 · 1250ca4c
      Josef Sipek 提交于
      Signed-off-by: NJosef Sipek <jsipek@fsl.cs.sunysb.edu>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      1250ca4c
    • P
      [PATCH] tty: ->signal->tty locking · 24ec839c
      Peter Zijlstra 提交于
      Fix the locking of signal->tty.
      
      Use ->sighand->siglock to protect ->signal->tty; this lock is already used
      by most other members of ->signal/->sighand.  And unless we are 'current'
      or the tasklist_lock is held we need ->siglock to access ->signal anyway.
      
      (NOTE: sys_unshare() is broken wrt ->sighand locking rules)
      
      Note that tty_mutex is held over tty destruction, so while holding
      tty_mutex any tty pointer remains valid.  Otherwise the lifetime of ttys
      are governed by their open file handles.  This leaves some holes for tty
      access from signal->tty (or any other non file related tty access).
      
      It solves the tty SLAB scribbles we were seeing.
      
      (NOTE: the change from group_send_sig_info to __group_send_sig_info needs to
             be examined by someone familiar with the security framework, I think
             it is safe given the SEND_SIG_PRIV from other __group_send_sig_info
             invocations)
      
      [schwidefsky@de.ibm.com: 3270 fix]
      [akpm@osdl.org: various post-viro fixes]
      Signed-off-by: NPeter Zijlstra <a.p.zijlstra@chello.nl>
      Acked-by: NAlan Cox <alan@redhat.com>
      Cc: Oleg Nesterov <oleg@tv-sign.ru>
      Cc: Prarit Bhargava <prarit@redhat.com>
      Cc: Chris Wright <chrisw@sous-sol.org>
      Cc: Roland McGrath <roland@redhat.com>
      Cc: Stephen Smalley <sds@tycho.nsa.gov>
      Cc: James Morris <jmorris@namei.org>
      Cc: "David S. Miller" <davem@davemloft.net>
      Cc: Jeff Dike <jdike@addtoit.com>
      Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
      Cc: Jan Kara <jack@ucw.cz>
      Signed-off-by: NMartin Schwidefsky <schwidefsky@de.ibm.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      24ec839c
  4. 02 10月, 2006 1 次提交
  5. 30 9月, 2006 1 次提交
  6. 26 9月, 2006 1 次提交
  7. 01 7月, 2006 1 次提交
  8. 24 6月, 2006 1 次提交
  9. 20 3月, 2006 1 次提交
  10. 23 12月, 2005 1 次提交
  11. 30 8月, 2005 1 次提交
  12. 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