Thread (5 messages) 5 messages, 2 authors, 2016-08-31
STALE3564d

[PATCH] arm64: ni_syscall should be similar to other archs

From: catalin.marinas@arm.com (Catalin Marinas)
Date: 2016-08-25 11:00:08

On Thu, Jun 30, 2016 at 01:58:08PM +0000, Hallsmark, Per wrote:
Catalin Marinas wrote:
quoted
On Wed, Feb 24, 2016 at 03:54:59PM +0100, per.hallsmark at windriver.com wrote:
quoted
From: Per Hallsmark <redacted>

Today arm64 have it's own variant when a userspace app is doing a
non-implemented syscall in that it dumps on console process name,
registers and such. This makes a different behaviour on arm64 than
on all other archs.
Are you hitting a real issue with this? Test apps doing random syscalls?
The issue was found on a real case, running lttng that tries to make use
of sys_brk before falling back to internal variant. On arm64 this generates
an "ugly" dump on console which dont happen on arm, x86 etc.
Why would a sys_brk() end up on the do_ni_syscall() path?

-- 
Catalin
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help