1. 24 2月, 2010 1 次提交
  2. 12 2月, 2010 1 次提交
    • S
      ptrace: Add support for generic PTRACE_GETREGSET/PTRACE_SETREGSET · 2225a122
      Suresh Siddha 提交于
      Generic support for PTRACE_GETREGSET/PTRACE_SETREGSET commands which
      export the regsets supported by each architecture using the correponding
      NT_* types. These NT_* types are already part of the userland ABI, used
      in representing the architecture specific register sets as different NOTES
      in an ELF core file.
      
      'addr' parameter for the ptrace system call encode the REGSET type (using
      the corresppnding NT_* type) and the 'data' parameter points to the
      struct iovec having the user buffer and the length of that buffer.
      
      	struct iovec iov = { buf, len};
      	ret = ptrace(PTRACE_GETREGSET/PTRACE_SETREGSET, pid, NT_XXX_TYPE, &iov);
      
      On successful completion, iov.len will be updated by the kernel specifying
      how much the kernel has written/read to/from the user's iov.buf.
      
      x86 extended state registers are primarily exported using this interface.
      Signed-off-by: NSuresh Siddha <suresh.b.siddha@intel.com>
      LKML-Reference: <20100211195614.886724710@sbs-t61.sc.intel.com>
      Acked-by: NHongjiu Lu <hjl.tools@gmail.com>
      Cc: Roland McGrath <roland@redhat.com>
      Signed-off-by: NH. Peter Anvin <hpa@zytor.com>
      2225a122
  3. 16 12月, 2009 2 次提交
  4. 19 6月, 2009 1 次提交
  5. 07 4月, 2009 1 次提交
  6. 03 4月, 2009 2 次提交
  7. 20 12月, 2008 1 次提交
    • M
      x86, bts: add fork and exit handling · bf53de90
      Markus Metzger 提交于
      Impact: introduce new ptrace facility
      
      Add arch_ptrace_untrace() function that is called when the tracer
      detaches (either voluntarily or when the tracing task dies);
      ptrace_disable() is only called on a voluntary detach.
      
      Add ptrace_fork() and arch_ptrace_fork(). They are called when a
      traced task is forked.
      
      Clear DS and BTS related fields on fork.
      
      Release DS resources and reclaim memory in ptrace_untrace(). This
      releases resources already when the tracing task dies. We used to do
      that when the traced task dies.
      Signed-off-by: NMarkus Metzger <markus.t.metzger@intel.com>
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      bf53de90
  8. 20 10月, 2008 1 次提交
  9. 08 8月, 2008 1 次提交
    • R
      tracehook: fix CLONE_PTRACE · 5861bbfc
      Roland McGrath 提交于
      In the change in commit 09a05394, I
      overlooked two nits in the logic and this broke using CLONE_PTRACE
      when PTRACE_O_TRACE* are not being used.
      
      A parent that is itself traced at all but not using PTRACE_O_TRACE*,
      using CLONE_PTRACE would have its new child fail to be traced.
      
      A parent that is not itself traced at all that uses CLONE_PTRACE
      (which should be a no-op in this case) would confuse the bookkeeping
      and lead to a crash at exit time.
      
      This restores the missing checks and fixes both failure modes.
      Reported-by: NEduardo Habkost <ehabkost@redhat.com>
      Signed-off-by: NRoland McGrath <roland@redhat.com>
      5861bbfc
  10. 27 7月, 2008 4 次提交
    • R
      task_current_syscall · bbc69863
      Roland McGrath 提交于
      This adds the new function task_current_syscall() on machines where the
      asm/syscall.h interface is supported (CONFIG_HAVE_ARCH_TRACEHOOK).  It's
      exported for modules to use in the future.  This function safely samples
      the state of a blocked thread to collect what system call it is blocked
      in, and the six system call argument registers.
      Signed-off-by: NRoland McGrath <roland@redhat.com>
      Cc: Oleg Nesterov <oleg@tv-sign.ru>
      Reviewed-by: NIngo Molnar <mingo@elte.hu>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      bbc69863
    • R
      tracehook: release_task · dae33574
      Roland McGrath 提交于
      This moves the ptrace-related logic from release_task into tracehook.h and
      ptrace.h inlines.  It provides clean hooks both before and after locking
      tasklist_lock, for future tracing logic to do more cleanup without the
      lock.
      
      This also changes release_task() itself in the rare "zap_leader" case to
      set the leader to EXIT_DEAD before iterating.  This maintains the
      invariant that release_task() only ever handles a task in EXIT_DEAD.  This
      is a common-sense invariant that is already always true except in this one
      arcane case of zombie leader whose parent ignores SIGCHLD.
      
      This change is harmless and only costs one store in this one rare case.
      It keeps the expected state more consisently sane, which is nicer when
      debugging weirdness in release_task().  It also lets some future code in
      the tracehook entry points rely on this invariant for bookkeeping.
      Signed-off-by: NRoland McGrath <roland@redhat.com>
      Cc: Oleg Nesterov <oleg@tv-sign.ru>
      Reviewed-by: NIngo Molnar <mingo@elte.hu>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      dae33574
    • R
      tracehook: clone · 09a05394
      Roland McGrath 提交于
      This moves all the ptrace initialization and tracing logic for task
      creation into tracehook.h and ptrace.h inlines.  It reorganizes the code
      slightly, but should not change any behavior.
      
      There are four tracehook entry points, at each important stage of task
      creation.  This keeps the interface from the core fork.c code fairly
      clean, while supporting the complex setup required for ptrace or something
      like it.
      Signed-off-by: NRoland McGrath <roland@redhat.com>
      Cc: Oleg Nesterov <oleg@tv-sign.ru>
      Reviewed-by: NIngo Molnar <mingo@elte.hu>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      09a05394
    • R
      tracehook: add linux/tracehook.h · 88ac2921
      Roland McGrath 提交于
      This patch series introduces the "tracehook" interface layer of inlines in
      <linux/tracehook.h>.  There are more details in the log entry for patch
      01/23 and in the header file comments inside that patch.  Most of these
      changes move code around with little or no change, and they should not
      break anything or change any behavior.
      
      This sets a new standard for uniform arch support to enable clean
      arch-independent implementations of new debugging and tracing stuff,
      denoted by CONFIG_HAVE_ARCH_TRACEHOOK.  Patch 20/23 adds that symbol to
      arch/Kconfig, with comments listing everything an arch has to do before
      setting "select HAVE_ARCH_TRACEHOOK".  These are elaborted a bit at:
      
      	http://sourceware.org/systemtap/wiki/utrace/arch/HowTo
      
      The new inlines that arch code must define or call have detailed kerneldoc
      comments in the generic header files that say what is required.
      
      No arch is obligated to do any work, and no arch's build should be broken
      by these changes.  There are several steps that each arch should take so
      it can set HAVE_ARCH_TRACEHOOK.  Most of these are simple.  Providing this
      support will let new things people add for doing debugging and tracing of
      user-level threads "just work" for your arch in the future.  For an arch
      that does not provide HAVE_ARCH_TRACEHOOK, some new options for such
      features will not be available for config.
      
      I have done some arch work and will submit this to the arch maintainers
      after the generic tracehook series settles in.  For now, that work is
      available in my GIT repositories, and in patch and mbox-of-patches form at
      http://people.redhat.com/roland/utrace/2.6-current/
      
      This paves the way for my "utrace" work, to be submitted later.  But it is
      not innately tied to that.  I hope that the tracehook series can go in
      soon regardless of what eventually does or doesn't go on top of it.  For
      anyone implementing any kind of new tracing/debugging plan, or just
      understanding all the context of the existing ptrace implementation,
      having tracehook.h makes things much easier to find and understand.
      
      This patch:
      
      This adds the new kernel-internal header file <linux/tracehook.h>.  This
      is not yet used at all.  The comments in the header introduce what the
      following series of patches is about.
      
      The aim is to formalize and consolidate all the places that the core
      kernel code and the arch code now ties into the ptrace implementation.
      
      These patches mostly don't cause any functional change.  They just move
      the details of ptrace logic out of core code into tracehook.h inlines,
      where they are mostly compiled away to the same as before.  All that
      changes is that everything is thoroughly documented and any future
      reworking of ptrace, or addition of something new, would not have to touch
      core code all over, just change the tracehook.h inlines.
      
      The new linux/ptrace.h inlines are used by the following patches in the
      new tracehook_*() inlines.  Using these helpers for the ptrace event stops
      makes it simple to change or disable the old ptrace implementation of
      these stops conditionally later.
      Signed-off-by: NRoland McGrath <roland@redhat.com>
      Cc: Oleg Nesterov <oleg@tv-sign.ru>
      Reviewed-by: NIngo Molnar <mingo@elte.hu>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      88ac2921
  11. 14 7月, 2008 1 次提交
    • S
      Security: split proc ptrace checking into read vs. attach · 006ebb40
      Stephen Smalley 提交于
      Enable security modules to distinguish reading of process state via
      proc from full ptrace access by renaming ptrace_may_attach to
      ptrace_may_access and adding a mode argument indicating whether only
      read access or full attach access is requested.  This allows security
      modules to permit access to reading process state without granting
      full ptrace access.  The base DAC/capability checking remains unchanged.
      
      Read access to /proc/pid/mem continues to apply a full ptrace attach
      check since check_mem_permission() already requires the current task
      to already be ptracing the target.  The other ptrace checks within
      proc for elements like environ, maps, and fds are changed to pass the
      read mode instead of attach.
      
      In the SELinux case, we model such reading of process state as a
      reading of a proc file labeled with the target process' label.  This
      enables SELinux policy to permit such reading of process state without
      permitting control or manipulation of the target process, as there are
      a number of cases where programs probe for such information via proc
      but do not need to be able to control the target (e.g. procps,
      lsof, PolicyKit, ConsoleKit).  At present we have to choose between
      allowing full ptrace in policy (more permissive than required/desired)
      or breaking functionality (or in some cases just silencing the denials
      via dontaudit rules but this can hide genuine attacks).
      
      This version of the patch incorporates comments from Casey Schaufler
      (change/replace existing ptrace_may_attach interface, pass access
      mode), and Chris Wright (provide greater consistency in the checking).
      
      Note that like their predecessors __ptrace_may_attach and
      ptrace_may_attach, the __ptrace_may_access and ptrace_may_access
      interfaces use different return value conventions from each other (0
      or -errno vs. 1 or 0).  I retained this difference to avoid any
      changes to the caller logic but made the difference clearer by
      changing the latter interface to return a bool rather than an int and
      by adding a comment about it to ptrace.h for any future callers.
      Signed-off-by: NStephen Smalley <sds@tycho.nsa.gov>
      Acked-by: NChris Wright <chrisw@sous-sol.org>
      Signed-off-by: NJames Morris <jmorris@namei.org>
      006ebb40
  12. 30 4月, 2008 1 次提交
  13. 09 2月, 2008 1 次提交
  14. 07 2月, 2008 1 次提交
    • R
      Add arch_ptrace_stop · 1a669c2f
      Roland McGrath 提交于
      This adds support to allow asm/ptrace.h to define two new macros,
      arch_ptrace_stop_needed and arch_ptrace_stop.  These control special
      machine-specific actions to be done before a ptrace stop.  The new code
      compiles away to nothing when the new macros are not defined.  This is the
      case on all machines to begin with.
      
      On ia64, these macros will be defined to solve the long-standing issue of
      ptrace vs register backing store.
      Signed-off-by: NRoland McGrath <roland@redhat.com>
      Cc: Petr Tesarik <ptesarik@suse.cz>
      Cc: Tony Luck <tony.luck@intel.com>
      Cc: Matthew Wilcox <willy@debian.org>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      1a669c2f
  15. 30 1月, 2008 3 次提交
  16. 03 1月, 2008 1 次提交
  17. 18 7月, 2007 2 次提交
  18. 30 9月, 2006 1 次提交
  19. 27 6月, 2006 1 次提交
  20. 23 6月, 2006 1 次提交
    • E
      [PATCH] ptrace: document the locking rules · 260ea101
      Eric W. Biederman 提交于
      After a lot of reading the code and thinking about how it behaves I have
      managed to figure out what the current ptrace locking rules are.  The
      current code is in much better that it appears at first glance.  The
      troublesome code paths are actually the code paths that violate the current
      rules.
      
      ptrace uses simple exclusive access as it's locking.  You can only touch
      task->ptrace if the task is stopped and you are the ptracer, or if the task
      is running and are the task itself.
      
      Very simple, very easy to maintain.  It just needs to be documented so
      people know not to touch ptrace from elsewhere.
      
      Currently we do have a few pieces of code that are in violation of this
      rule.  Particularly the core dump code, and ptrace_attach.  But so far the
      code looks fixable.
      Signed-off-by: NEric W. Biederman <ebiederm@xmission.com>
      Cc: Oleg Nesterov <oleg@tv-sign.ru>
      Cc: Roland McGrath <roland@redhat.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      260ea101
  21. 16 2月, 2006 1 次提交
  22. 09 1月, 2006 2 次提交
  23. 07 11月, 2005 1 次提交
  24. 08 9月, 2005 1 次提交
  25. 05 9月, 2005 2 次提交
    • B
      [PATCH] Uml support: add PTRACE_SYSEMU_SINGLESTEP option to i386 · 1b38f006
      Bodo Stroesser 提交于
      This patch implements the new ptrace option PTRACE_SYSEMU_SINGLESTEP, which
      can be used by UML to singlestep a process: it will receive SINGLESTEP
      interceptions for normal instructions and syscalls, but syscall execution will
      be skipped just like with PTRACE_SYSEMU.
      Signed-off-by: NBodo Stroesser <bstroesser@fujitsu-siemens.com>
      Signed-off-by: NPaolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
      Cc: Jeff Dike <jdike@addtoit.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      1b38f006
    • L
      [PATCH] UML Support - Ptrace: adds the host SYSEMU support, for UML and general usage · ed75e8d5
      Laurent Vivier 提交于
            Jeff Dike <jdike@addtoit.com>,
            Paolo 'Blaisorblade' Giarrusso <blaisorblade_spam@yahoo.it>,
            Bodo Stroesser <bstroesser@fujitsu-siemens.com>
      
      Adds a new ptrace(2) mode, called PTRACE_SYSEMU, resembling PTRACE_SYSCALL
      except that the kernel does not execute the requested syscall; this is useful
      to improve performance for virtual environments, like UML, which want to run
      the syscall on their own.
      
      In fact, using PTRACE_SYSCALL means stopping child execution twice, on entry
      and on exit, and each time you also have two context switches; with SYSEMU you
      avoid the 2nd stop and so save two context switches per syscall.
      
      Also, some architectures don't have support in the host for changing the
      syscall number via ptrace(), which is currently needed to skip syscall
      execution (UML turns any syscall into getpid() to avoid it being executed on
      the host).  Fixing that is hard, while SYSEMU is easier to implement.
      
      * This version of the patch includes some suggestions of Jeff Dike to avoid
        adding any instructions to the syscall fast path, plus some other little
        changes, by myself, to make it work even when the syscall is executed with
        SYSENTER (but I'm unsure about them). It has been widely tested for quite a
        lot of time.
      
      * Various fixed were included to handle the various switches between
        various states, i.e. when for instance a syscall entry is traced with one of
        PT_SYSCALL / _SYSEMU / _SINGLESTEP and another one is used on exit.
        Basically, this is done by remembering which one of them was used even after
        the call to ptrace_notify().
      
      * We're combining TIF_SYSCALL_EMU with TIF_SYSCALL_TRACE or TIF_SINGLESTEP
        to make do_syscall_trace() notice that the current syscall was started with
        SYSEMU on entry, so that no notification ought to be done in the exit path;
        this is a bit of a hack, so this problem is solved in another way in next
        patches.
      
      * Also, the effects of the patch:
      "Ptrace - i386: fix Syscall Audit interaction with singlestep"
      are cancelled; they are restored back in the last patch of this series.
      
      Detailed descriptions of the patches doing this kind of processing follow (but
      I've already summed everything up).
      
      * Fix behaviour when changing interception kind #1.
      
        In do_syscall_trace(), we check the status of the TIF_SYSCALL_EMU flag
        only after doing the debugger notification; but the debugger might have
        changed the status of this flag because he continued execution with
        PTRACE_SYSCALL, so this is wrong.  This patch fixes it by saving the flag
        status before calling ptrace_notify().
      
      * Fix behaviour when changing interception kind #2:
        avoid intercepting syscall on return when using SYSCALL again.
      
        A guest process switching from using PTRACE_SYSEMU to PTRACE_SYSCALL
        crashes.
      
        The problem is in arch/i386/kernel/entry.S.  The current SYSEMU patch
        inhibits the syscall-handler to be called, but does not prevent
        do_syscall_trace() to be called after this for syscall completion
        interception.
      
        The appended patch fixes this.  It reuses the flag TIF_SYSCALL_EMU to
        remember "we come from PTRACE_SYSEMU and now are in PTRACE_SYSCALL", since
        the flag is unused in the depicted situation.
      
      * Fix behaviour when changing interception kind #3:
        avoid intercepting syscall on return when using SINGLESTEP.
      
        When testing 2.6.9 and the skas3.v6 patch, with my latest patch and had
        problems with singlestepping on UML in SKAS with SYSEMU.  It looped
        receiving SIGTRAPs without moving forward.  EIP of the traced process was
        the same for all SIGTRAPs.
      
      What's missing is to handle switching from PTRACE_SYSCALL_EMU to
      PTRACE_SINGLESTEP in a way very similar to what is done for the change from
      PTRACE_SYSCALL_EMU to PTRACE_SYSCALL_TRACE.
      
      I.e., after calling ptrace(PTRACE_SYSEMU), on the return path, the debugger is
      notified and then wake ups the process; the syscall is executed (or skipped,
      when do_syscall_trace() returns 0, i.e.  when using PTRACE_SYSEMU), and
      do_syscall_trace() is called again.  Since we are on the return path of a
      SYSEMU'd syscall, if the wake up is performed through ptrace(PTRACE_SYSCALL),
      we must still avoid notifying the parent of the syscall exit.  Now, this
      behaviour is extended even to resuming with PTRACE_SINGLESTEP.
      Signed-off-by: NPaolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
      Cc: Jeff Dike <jdike@addtoit.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      ed75e8d5
  26. 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