Golang 与系统调用
什么是系统调用先看下wiki的定义: In computing,a system call is the programmatic way in which a computer program requests a service from the kernel of the operating system it is executed on. This may include hardware-related services (for example,accessing a hard disk drive),creation and execution of new processes,and communication with integral kernel services such as process scheduling. System calls provide an essential interface between a process and the operating system. 系统调用是程序向操作系统内核请求服务的过程,通常包含硬件相关的服务(例如访问硬盘),创建新进程等。系统调用提供了一个进程和操作系统之间的接口。 syscall无处不在只要在os上写程序,就无法避免和syscall打交道。举个最常用的例子, func Fprintln(w io.Writer,a ...interface{}) (n int,err error) { p := newPrinter() p.doPrintln(a) // writer 是 stdout n,err = w.Write(p.buf) p.free() return } Stdout = NewFile(uintptr(syscall.Stdout),"/dev/stdout") func (f *File) write(b []byte) (n int,err error) { if len(b) == 0 { return 0,nil } // 实际的write方法,就是调用syscall.Write() return fixCount(syscall.Write(f.fd,b)) } Zero-Copy再举一个例子,我们常听到的 zero-copy,我们看看zero-copy是用来解决什么问题的。 read(file,tmp_buf,len); write(socket,len); 借用一张图来说明问题
我们看到,这里数据在用户空间和内核空间来回拷贝,其实是不必要的。 解决的办法有: 到这里我们应该对系统调用有了一定的认识了。 Strace
strace <bin> strace -p <pid> // 用于统计各个系统调用的次数 strace -c <bin> // 例如 strace -c echo hello hello % time seconds usecs/call calls errors syscall ------ ----------- ----------- --------- --------- ---------------- 0.00 0.000000 0 1 read 0.00 0.000000 0 1 write 0.00 0.000000 0 3 open 0.00 0.000000 0 5 close 0.00 0.000000 0 4 fstat 0.00 0.000000 0 7 mmap 0.00 0.000000 0 4 mprotect 0.00 0.000000 0 1 munmap 0.00 0.000000 0 3 brk 0.00 0.000000 0 3 3 access 0.00 0.000000 0 1 execve 0.00 0.000000 0 1 arch_prctl ------ ----------- ----------- --------- --------- ---------------- 100.00 0.000000 34 3 total stace 的实现原理是系统调用 ptrace,我们来看下 ptrace 是什么。 Ptraceman page 描述如下: The ptrace() system call provides a means by which one process (the "tracer") may observe and control the execution of another process (the "tracee"),and examine and change the tracee's memory and registers. It is primarily used to implement breakpoint debuggingand system call tracing. 简单来说有三大能力:
接口int ptrace(int request,pid_t pid,caddr_t addr,int data); request包含: PTRACE_ATTACH PTRACE_SYSCALL PTRACE_PEEKTEXT,PTRACE_PEEKDATA 等 tracer 使用 接着,tracer 继续调用 myStrace了解以上内容后,presenter 现场实现了一个go版本的strace,需要在 linux amd64 环境编译。 // strace.go package main import ( "fmt" "os" "os/exec" "syscall" ) func main() { var err error var regs syscall.PtraceRegs var ss syscallCounter ss = ss.init() fmt.Println("Run: ",os.Args[1:]) cmd := exec.Command(os.Args[1],os.Args[2:]...) cmd.Stderr = os.Stderr cmd.Stdout = os.Stdout cmd.Stdin = os.Stdin cmd.SysProcAttr = &syscall.SysProcAttr{ Ptrace: true,} cmd.Start() err = cmd.Wait() if err != nil { fmt.Printf("Wait err %v n",err) } pid := cmd.Process.Pid exit := true for { // 记得 PTRACE_SYSCALL 会在进入和退出syscall时使 tracee 暂停,所以这里用一个变量控制,RAX的内容只打印一遍 if exit { err = syscall.PtraceGetRegs(pid,®s) if err != nil { break } //fmt.Printf("%#v n",regs) name := ss.getName(regs.Orig_rax) fmt.Printf("name: %s,id: %d n",name,regs.Orig_rax) ss.inc(regs.Orig_rax) } // 上面Ptrace有提到的一个request命令 err = syscall.PtraceSyscall(pid,0) if err != nil { panic(err) } // 猜测是等待进程进入下一个stop,这里如果不等待,那么会打印大量重复的调用函数名 _,err = syscall.Wait4(pid,nil,nil) if err != nil { panic(err) } exit = !exit } ss.print() } // 用于统计信息的counter,syscallcounter.go package main import ( "fmt" "os" "text/tabwriter" "github.com/seccomp/libseccomp-golang" ) type syscallCounter []int const maxSyscalls = 303 func (s syscallCounter) init() syscallCounter { s = make(syscallCounter,maxSyscalls) return s } func (s syscallCounter) inc(syscallID uint64) error { if syscallID > maxSyscalls { return fmt.Errorf("invalid syscall ID (%x)",syscallID) } s[syscallID]++ return nil } func (s syscallCounter) print() { w := tabwriter.NewWriter(os.Stdout,8,' ',tabwriter.AlignRight|tabwriter.Debug) for k,v := range s { if v > 0 { name,_ := seccomp.ScmpSyscall(k).GetName() fmt.Fprintf(w,"%dt%sn",v,name) } } w.Flush() } func (s syscallCounter) getName(syscallID uint64) string { name,_ := seccomp.ScmpSyscall(syscallID).GetName() return name } 最后结果: Run: [echo hello] Wait err stop signal: trace/breakpoint trap name: execve,id: 59 name: brk,id: 12 name: access,id: 21 name: mmap,id: 9 name: access,id: 21 name: open,id: 2 name: fstat,id: 5 name: mmap,id: 9 name: close,id: 3 name: access,id: 2 name: read,id: 0 name: fstat,id: 9 name: mprotect,id: 10 name: mmap,id: 9 name: mmap,id: 3 name: mmap,id: 9 name: arch_prctl,id: 158 name: mprotect,id: 10 name: mprotect,id: 10 name: munmap,id: 11 name: brk,id: 12 name: brk,id: 12 name: open,id: 3 name: fstat,id: 5 hello name: write,id: 1 name: close,id: 3 name: close,id: 3 1|read 1|write 3|open 5|close 4|fstat 7|mmap 4|mprotect 1|munmap 3|brk 3|access 1|execve 1|arch_prctl 对比一下结果,可以发现和 strace 是一样的。 presenter github (编辑:李大同) 【声明】本站内容均来自网络,其相关言论仅代表作者个人观点,不代表本站立场。若无意侵犯到您的权利,请及时与联系站长删除相关内容! |