我是靠谱客的博主 欣喜冬瓜,最近开发中收集的这篇文章主要介绍ptrace linux,ptrace在Linux中如何工作?,觉得挺不错的,现在分享给大家,希望可以做个参考。

概述

When the attached child process invokes a system call, the ptracing parent process can be notified. But how exactly does that happen?

父进程使用PTRACE_ATTACH调用ptrace,并且他的孩子使用PTRACE_TRACEME选项调用ptrace.该对将通过填充其内部的一些字段来连接两个进程(kernel/ptrace.c: sys_ptrace,子进程将在struct task_struct的ptrace字段中具有PT_PTRACED标志,将ptr的进程作为父进程和ptrace_entry列表中的pid – __ptrace_link;父进程将在ptraced列表中记录小孩的pid ).

然后strace将使用PTRACE_SYSCALL标志调用ptrace,将其注册为syscall调试器,在子进程的struct thread_info(通过类似于set_tsk_thread_flag(child,TIF_SYSCALL_TRACE))中设置thread_flag TIF_SYSCALL_TRACE. arch/x86/include/asm/thread_info.h:

67 /*

68 * thread information flags

69 * - these are process state flags that various assembly files

70 * may need to access ...*/

75 #define TIF_SYSCALL_TRACE 0 /* syscall trace active */

99 #define _TIF_SYSCALL_TRACE (1 << TIF_SYSCALL_TRACE)

在每个系统调用进入或退出时,特定于体系结构的系统调用代码将检查此_TIF_SYSCALL_TRACE flag(直接在系统调用程序的汇编程序中执行,例如x86 arch/x86/kernel/entry_32.S:ENTRY(system_call)中的jnz syscall_trace_entry和syscall_exit_work中的类似代码),如果已设置, ptracer将通过信号(SIGTRAP)通知,孩子将被暂时停止.这通常在syscall_trace_enter和syscall_trace_leave中完成:

1457 long syscall_trace_enter(struct pt_regs *regs)

1483 if ((ret || test_thread_flag(TIF_SYSCALL_TRACE)) &&

1484 tracehook_report_syscall_entry(regs))

1485 ret = -1L;

1507 void syscall_trace_leave(struct pt_regs *regs)

1531 if (step || test_thread_flag(TIF_SYSCALL_TRACE))

1532 tracehook_report_syscall_exit(regs, step);

tracehook_report_syscall_ *是这里的实际工作人员,他们会调用ptrace_report_syscall. include/linux/tracehook.h:

80 /**

81 * tracehook_report_syscall_entry - task is about to attempt a system call

82 * @regs: user register state of current task

83 *

84 * This will be called if %TIF_SYSCALL_TRACE has been set, when the

85 * current task has just entered the kernel for a system call.

86 * Full user register state is available here. Changing the values

87 * in @regs can affect the system call number and arguments to be tried.

88 * It is safe to block here, preventing the system call from beginning.

89 *

90 * Returns zero normally, or nonzero if the calling arch code should abort

91 * the system call. That must prevent normal entry so no system call is

92 * made. If @task ever returns to user mode after this, its register state

93 * is unspecified, but should be something harmless like an %ENOSYS error

94 * return. It should preserve enough information so that syscall_rollback()

95 * can work (see asm-generic/syscall.h).

96 *

97 * Called without locks, just after entering kernel mode.

98 */

99 static inline __must_check int tracehook_report_syscall_entry(

100 struct pt_regs *regs)

101 {

102 return ptrace_report_syscall(regs);

103 }

104

105 /**

106 * tracehook_report_syscall_exit - task has just finished a system call

107 * @regs: user register state of current task

108 * @step: nonzero if simulating single-step or block-step

109 *

110 * This will be called if %TIF_SYSCALL_TRACE has been set, when the

111 * current task has just finished an attempted system call. Full

112 * user register state is available here. It is safe to block here,

113 * preventing signals from being processed.

114 *

115 * If @step is nonzero, this report is also in lieu of the normal

116 * trap that would follow the system call instruction because

117 * user_enable_block_step() or user_enable_single_step() was used.

118 * In this case, %TIF_SYSCALL_TRACE might not be set.

119 *

120 * Called without locks, just before checking for pending signals.

121 */

122 static inline void tracehook_report_syscall_exit(struct pt_regs *regs, int step)

123 {

...

130

131 ptrace_report_syscall(regs);

132 }

和ptrace_report_syscall generates SIGTRAP调试器或strace通过ptrace_notify / ptrace_do_notify:

55 /*

56 * ptrace report for syscall entry and exit looks identical.

57 */

58 static inline int ptrace_report_syscall(struct pt_regs *regs)

59 {

60 int ptrace = current->ptrace;

61

62 if (!(ptrace & PT_PTRACED))

63 return 0;

64

65 ptrace_notify(SIGTRAP | ((ptrace & PT_TRACESYSGOOD) ? 0x80 : 0));

66

67 /*

68 * this isn't the same as continuing with a signal, but it will do

69 * for normal use. strace only continues with a signal if the

70 * stopping signal is not SIGTRAP. -brl

71 */

72 if (current->exit_code) {

73 send_sig(current->exit_code, current, 1);

74 current->exit_code = 0;

75 }

76

77 return fatal_signal_pending(current);

78 }

ptrace_notify在kernel/signal.c实现,它停止了孩子,并将sig_info传递给ptracer:

1961 static void ptrace_do_notify(int signr, int exit_code, int why)

1962 {

1963 siginfo_t info;

1964

1965 memset(&info, 0, sizeof info);

1966 info.si_signo = signr;

1967 info.si_code = exit_code;

1968 info.si_pid = task_pid_vnr(current);

1969 info.si_uid = from_kuid_munged(current_user_ns(), current_uid());

1970

1971 /* Let the debugger run. */

1972 ptrace_stop(exit_code, why, 1, &info);

1973 }

1974

1975 void ptrace_notify(int exit_code)

1976 {

1977 BUG_ON((exit_code & (0x7f | ~0xffff)) != SIGTRAP);

1978 if (unlikely(current->task_works))

1979 task_work_run();

1980

1981 spin_lock_irq(&current->sighand->siglock);

1982 ptrace_do_notify(SIGTRAP, exit_code, CLD_TRAPPED);

1983 spin_unlock_irq(&current->sighand->siglock);

1984 }

ptrace_stop在同一个signal.c文件中,第1839行为3.13.

最后

以上就是欣喜冬瓜为你收集整理的ptrace linux,ptrace在Linux中如何工作?的全部内容,希望文章能够帮你解决ptrace linux,ptrace在Linux中如何工作?所遇到的程序开发问题。

如果觉得靠谱客网站的内容还不错,欢迎将靠谱客网站推荐给程序员好友。

本图文内容来源于网友提供,作为学习参考使用,或来自网络收集整理,版权属于原作者所有。
点赞(49)

评论列表共有 0 条评论

立即
投稿
返回
顶部