1. 10 4月, 2008 1 次提交
    • D
      [SPARC]: Fix several regset and ptrace bugs. · d786a4a6
      David S. Miller 提交于
      1) ptrace should pass 'current' to task_user_regset_view()
      
      2) When fetching general registers using a 64-bit view, and
         the target is 32-bit, we have to convert.
      
      3) Skip the whole register window get/set code block if
         the user isn't asking to access anything in there.
      
         Otherwise we have problems if the user doesn't have
         an address space setup.  Fetching ptrace register is
         still valid at such a time, and ptrace does not try
         to access the register window area of the regset.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      d786a4a6
  2. 07 2月, 2008 5 次提交
  3. 21 12月, 2007 1 次提交
  4. 20 10月, 2007 1 次提交
  5. 10 12月, 2006 1 次提交
  6. 13 1月, 2006 1 次提交
  7. 09 1月, 2006 1 次提交
  8. 01 5月, 2005 1 次提交
  9. 18 4月, 2005 1 次提交
    • D
      [PATCH] sparc: Fix PTRACE_CONT bogosity · fb65b961
      David S. Miller 提交于
      SunOS aparently had this weird PTRACE_CONT semantic which
      we copied.  If the addr argument is something other than
      1, it sets the process program counter to whatever that
      value is.
      
      This is different from every other Linux architecture, which
      don't do anything with the addr and data args.
      
      This difference in particular breaks the Linux native GDB support
      for fork and vfork tracing on sparc and sparc64.
      
      There is no interest in running SunOS binaries using this weird
      PTRACE_CONT behavior, so just delete it so we behave like other
      platforms do.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      fb65b961
  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