1. 14 1月, 2006 1 次提交
  2. 10 9月, 2005 1 次提交
  3. 10 6月, 2005 1 次提交
    • C
      [IA64] Fix race condition in the rt_sigprocmask fastcall · a2a64769
      Christoph Lameter 提交于
      current->blocked will be set to the value of current->thread_info->flags if the
      cmpxchg to update thread_info->flags fails. For performance reasons the store into
      current->blocked was placed in the cmpxchg loop. However, the cmpxchg overwrites the
      register holding the value to be stored. In the rare case of a retry the value of
      thread_info->flags will be written into current->blocked.
      
      The fix is to use another register so that the register containing the current->blocked
      value is not overwritten.
      Signed-off-by: NChristoph Lameter <clameter@sgi.com>
      Signed-off-by: NTony Luck <tony.luck@intel.com>
      a2a64769
  4. 06 5月, 2005 1 次提交
  5. 04 5月, 2005 1 次提交
    • D
      [IA64] fix ia64 syscall auditing · 446b8831
      David Woodhouse 提交于
      Attached is a patch against David's audit.17 kernel that adds checks
      for the TIF_SYSCALL_AUDIT thread flag to the ia64 system call and
      signal handling code paths.  The patch enables auditing of system
      calls set up via fsys_bubble_down, as well as ensuring that
      audit_syscall_exit() is called on return from sigreturn.
      
      Neglecting to check for TIF_SYSCALL_AUDIT at these points results in
      incorrect information in audit_context, causing frequent system panics
      when system call auditing is enabled on an ia64 system.
      
      I have tested this patch and have seen no problems with it.
      
      [Original patch from Amy Griffis ported to current kernel by David Woodhouse]
      
      From: Amy Griffis <amy.griffis@hp.com>
      From: David Woodhouse <dwmw2@infradead.org>
      Signed-off-by: NChris Wright <chrisw@osdl.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      Signed-off-by: NTony Luck <tony.luck@intel.com>
      446b8831
  6. 29 4月, 2005 1 次提交
    • A
      [PATCH] fix ia64 syscall auditing · 3ac3ed55
      Amy Griffis 提交于
      Attached is a patch against David's audit.17 kernel that adds checks
      for the TIF_SYSCALL_AUDIT thread flag to the ia64 system call and
      signal handling code paths.The patch enables auditing of system
      calls set up via fsys_bubble_down, as well as ensuring that
      audit_syscall_exit() is called on return from sigreturn.
      
      Neglecting to check for TIF_SYSCALL_AUDIT at these points results in
      incorrect information in audit_context, causing frequent system panics
      when system call auditing is enabled on an ia64 system.
      Signed-off-by: NAmy Griffis <amy.griffis@hp.com>
      Signed-off-by: NDavid Woodhouse <dwmw2@infradead.org>
      3ac3ed55
  7. 28 4月, 2005 2 次提交
    • D
      [IA64] Annotate fsys_bubble_down() with McKinley dispatch info. · fbf7192b
      David Mosberger-Tang 提交于
      This patch changes comments & formatting only.  There is no code
      change.
      Signed-off-by: NDavid Mosberger-Tang <davidm@hpl.hp.com>
      Signed-off-by: NTony Luck <tony.luck@intel.com>
      fbf7192b
    • D
      [IA64] Reschedule fsys_bubble_down(). · 1ba7be7d
      David Mosberger-Tang 提交于
      Improvements come from eliminating srlz.i, not scheduling AR/CR-reads
      too early (while there are others still pending), scheduling the
      backing-store switch as well as possible, splitting the BBB bundle
      into a MIB/MBB pair.
      
      Why is it safe to eliminate the srlz.i?  Observe
      that we used to clear bits ~PSR_PRESERVED_BITS in PSR.L.  Since
      PSR_PRESERVED_BITS==PSR.{UP,MFL,MFH,PK,DT,PP,SP,RT,IC}, we
      ended up clearing PSR.{BE,AC,I,DFL,DFH,DI,DB,SI,TB}.  However,
      
       PSR.BE : already is turned off in __kernel_syscall_via_epc()
       PSR.AC : don't care (kernel normally turns PSR.AC on)
       PSR.I  : already turned off by the time fsys_bubble_down gets invoked
       PSR.DFL: always 0 (kernel never turns it on)
       PSR.DFH: don't care --- kernel never touches f32-f127 on its own
      	  initiative
       PSR.DI : always 0 (kernel never turns it on)
       PSR.SI : always 0 (kernel never turns it on)
       PSR.DB : don't care --- kernel never enables kernel-level breakpoints
       PSR.TB : must be 0 already; if it wasn't zero on entry to
      	  __kernel_syscall_via_epc, the branch to fsys_bubble_down
      	  will trigger a taken branch; the taken-trap-handler then
      	  converts the syscall into a break-based system-call.
      
      In other words: all the bits we're clearying are either 0 already or
      are don't cares!  Thus, we don't have to write PSR.L at all and we
      don't have to do a srlz.i either.
      
      Good for another ~20 cycle improvement for EPC-based heavy-weight
      syscalls.
      Signed-off-by: NDavid Mosberger-Tang <davidm@hpl.hp.com>
      Signed-off-by: NTony Luck <tony.luck@intel.com>
      1ba7be7d
  8. 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