From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756570AbbAPP7p (ORCPT ); Fri, 16 Jan 2015 10:59:45 -0500 Received: from gw-1.arm.linux.org.uk ([78.32.30.217]:45051 "EHLO pandora.arm.linux.org.uk" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1756293AbbAPP7n (ORCPT ); Fri, 16 Jan 2015 10:59:43 -0500 Date: Fri, 16 Jan 2015 15:59:23 +0000 From: Russell King - ARM Linux To: Roman Peniaev Cc: Kees Cook , Will Deacon , Stefano Stabellini , Marc Zyngier , Catalin Marinas , Sekhar Nori , "linux-kernel@vger.kernel.org" , "stable@vger.kernel.org" , Christoffer Dall , "linux-arm-kernel@lists.infradead.org" Subject: Re: [PATCH 1/2] ARM: entry-common: fix forgotten set of thread_info->syscall Message-ID: <20150116155923.GK12302@n2100.arm.linux.org.uk> References: <1420986751-30364-1-git-send-email-r.peniaev@gmail.com> <1420986751-30364-2-git-send-email-r.peniaev@gmail.com> <20150112183955.GO13360@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Jan 17, 2015 at 12:57:02AM +0900, Roman Peniaev wrote: > On Fri, Jan 16, 2015 at 7:54 AM, Kees Cook 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.