On Sat, Jan 17, 2015 at 12:57:02AM +0900, Roman Peniaev wrote: > On Fri, Jan 16, 2015 at 7:54 AM, Kees Cook <keesc...@chromium.org> wrote: > > One interesting thing I noticed (which is unchanged by this series), > > but pulling ARM_r7 during the seccomp ptrace event shows __NR_poll, > > not __NR_restart_syscall, even though it was a __NR_restart_syscall > > trap from seccomp. Is there a better place to see the actual syscall? > > As I understand we do not push new r7 to the stack, and ptrace uses the > old value.
And why should we push r7 to the stack? ptrace should be using the recorded system call number, rather than poking about on the stack itself. -- FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up according to speedtest.net. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
