MIPS: secure_computing, syscall audit: syscall number should in r2, not r0.
authorAl Viro <viro@ftp.linux.org.uk>
Tue, 28 Sep 2010 17:50:27 +0000 (18:50 +0100)
committerRalf Baechle <ralf@linux-mips.org>
Mon, 18 Oct 2010 15:59:02 +0000 (16:59 +0100)
commite5b377a8fb7b05f27647698ac739a0504cb2bf80
tree709838474a29aa0b7e763fda587a875c4e98a824
parent062ab57b2f8439ab506645cf6f29432e7c61497c
MIPS: secure_computing, syscall audit: syscall number should in r2, not r0.

As it is, audit_syscall_entry() and secure_computing() get the
bogus value (0, in fact)

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Cc: linux-arch@vger.kernel.org
Cc: linux-mips@linux-mips.org
Patchwork: https://patchwork.linux-mips.org/patch/1697/
Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
arch/mips/kernel/ptrace.c