May 2019 Archives by date

• Messages sorted by: [ thread ] [ subject ] [ author ]
• More info on this list...

Starting: Fri May 3 04:05:58 UTC 2019
Ending: Wed May 29 14:25:16 UTC 2019
Messages: 41

• strace for m68k bpf_prog_info mismatch   Baruch Siach
• strace for m68k bpf_prog_info mismatch   Geert Uytterhoeven
• strace for m68k bpf_prog_info mismatch   Baruch Siach
• strace for m68k bpf_prog_info mismatch   Dmitry V. Levin
• strace for m68k bpf_prog_info mismatch   Geert Uytterhoeven
• [PATCH] Update ioctl entries from linux v5.1   Gleb Fotengauer-Malinovskiy
• GSoC warm up   Zhibin Li
• [PATCH linux-next v10 0/7] ptrace: add PTRACE_GET_SYSCALL_INFO request   Oleg Nesterov
• [PATCH v11 0/7] ptrace: add PTRACE_GET_SYSCALL_INFO request   Dmitry V. Levin
• [PATCH v11 6/7] ptrace: add PTRACE_GET_SYSCALL_INFO request   Dmitry V. Levin
• [PATCH v3 0/3] Stage output for -z and new -Z options   Paul Chaignon
• [PATCH v3 1/3] Existing -z option prints only successful syscalls. This patch adds a -Z option to print only failing syscalls.   Paul Chaignon
• [PATCH v3 2/3] The -z and -Z options print only successful and failing syscalls respectively. However, failure of syscall is only known after syscall return. Thus, we end up with something like this on, e.g., ENOENT:   Paul Chaignon
• [PATCH v3 2/3] The -z and -Z options print only successful and failing syscalls respectively. However, failure of syscall is only known after syscall return. Thus, we end up with something like this on, e.g., ENOENT:   Kohl, Burkhard
• I: GSoC 2019 community bonding period   Dmitry V. Levin
• I: GSoC 2019 community bonding period   Paul Chaignon
• [PATCH] Update ioctl entries from linux v5.1   Dmitry V. Levin
• strace for m68k bpf_prog_info mismatch   Dmitry V. Levin
• GSoC warm up   Dmitry V. Levin
• Q: tests/ioctl_kvm_run_common.c failing with KVM_EXIT_FAIL_ENTRY   Dmitry V. Levin
• [PATCH v3 3/3] This patch adds two test cases for the -z and -Z options.   Dmitry V. Levin
• [PATCH v3 2/3] The -z and -Z options print only successful and failing syscalls respectively. However, failure of syscall is only known after syscall return. Thus, we end up with something like this on, e.g., ENOENT:   Dmitry V. Levin
• Q: tests/ioctl_kvm_run_common.c failing with KVM_EXIT_FAIL_ENTRY   Masatake YAMATO
• [PATCH v3 2/3] The -z and -Z options print only successful and failing syscalls respectively. However, failure of syscall is only known after syscall return. Thus, we end up with something like this on, e.g., ENOENT:   Dmitry V. Levin
• [PATCH v3 2/3] The -z and -Z options print only successful and failing syscalls respectively. However, failure of syscall is only known after syscall return. Thus, we end up with something like this on, e.g., ENOENT:   Paul Chaignon
• [PATCH v3 2/3] The -z and -Z options print only successful and failing syscalls respectively. However, failure of syscall is only known after syscall return. Thus, we end up with something like this on, e.g., ENOENT:   Dmitry V. Levin
• [PATCH v3 2/3] The -z and -Z options print only successful and failing syscalls respectively. However, failure of syscall is only known after syscall return. Thus, we end up with something like this on, e.g., ENOENT:   Paul Chaignon
• [PATCH v3 2/3] The -z and -Z options print only successful and failing syscalls respectively. However, failure of syscall is only known after syscall return. Thus, we end up with something like this on, e.g., ENOENT:   Dmitry V. Levin
• strace 5.1 released   Dmitry V. Levin
• GSoC warm up   Zhibin Li
• [PATCH] tests,kvm: print the reason of failure   Masatake YAMATO
• Q: tests/ioctl_kvm_run_common.c failing with KVM_EXIT_FAIL_ENTRY   Masatake YAMATO
• Q: tests/ioctl_kvm_run_common.c failing with KVM_EXIT_FAIL_ENTRY   Dmitry V. Levin
• [PATCH v3 2/3] The -z and -Z options print only successful and failing syscalls respectively. However, failure of syscall is only known after syscall return. Thus, we end up with something like this on, e.g., ENOENT:   Paul Chaignon
• [PATCH v3 2/3] The -z and -Z options print only successful and failing syscalls respectively. However, failure of syscall is only known after syscall return. Thus, we end up with something like this on, e.g., ENOENT:   Kohl, Burkhard
• [PATCH v3 2/3] The -z and -Z options print only successful and failing syscalls respectively. However, failure of syscall is only known after syscall return. Thus, we end up with something like this on, e.g., ENOENT:   Dmitry V. Levin
• I: GSoC status reports   Dmitry V. Levin
• Questions about git co-author   Zhibin Li
• Questions about git co-author   Paul Chaignon
• Questions about git co-author   Dmitry V. Levin
• Questions about git co-author   Patrik Jakobsson

Last message date: Wed May 29 14:25:16 UTC 2019
Archived on: Wed May 29 14:25:26 UTC 2019

• Messages sorted by: [ thread ] [ subject ] [ author ]
• More info on this list...