sparc: Fix system call tracing register handling.

Browse source

[ Upstream commit 1a40b95374 ]

A system call trace trigger on entry allows the tracing
process to inspect and potentially change the traced
process's registers.

Account for that by reloading the %g1 (syscall number)
and %i0-%i5 (syscall argument) values.  We need to be
careful to revalidate the range of %g1, and reload the
system call table entry it corresponds to into %l7.

Reported-by: Mike Frysinger <vapier@gentoo.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
Tested-by: Mike Frysinger <vapier@gentoo.org>
Signed-off-by: Sasha Levin <sasha.levin@oracle.com>

...

This commit is contained in:

Mike Frysinger 2016-01-18 06:32:30 -05:00 • committed by Sasha Levin

parent 25b37ef7db

commit 2129cf58c0

2 changed files with 53 additions and 0 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

17

arch/sparc/kernel/entry.S

View file

36

arch/sparc/kernel/syscalls.S

View file