linux-kernel - Re: [PATCH] arm64: ftrace: Fix to enable syscall events on arm64

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20181127131859.79ce7da9@gandalf.local.home>
Date:   Tue, 27 Nov 2018 13:18:59 -0500
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Will Deacon <will.deacon@....com>
Cc:     Masami Hiramatsu <mhiramat@...nel.org>,
        Catalin Marinas <catalin.marinas@....com>,
        Naresh Kamboju <naresh.kamboju@...aro.org>,
        Mark Rutland <mark.rutland@....com>,
        Ingo Molnar <mingo@...hat.com>,
        Masami Hiramatsu <masami.hiramatsu@...aro.org>,
        linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH] arm64: ftrace: Fix to enable syscall events on arm64

On Tue, 27 Nov 2018 16:58:49 +0000
Will Deacon <will.deacon@....com> wrote:

> This looks fine to me, but I'm curious about whether this is supposed to
> work with compat syscalls as well, where the prefix is "__arm64_compat_".
> 
> If we broadly follow the x86 lead, we'd have:
> 
> 	return (!strncmp(sym, "__arm64_", 8) && !strcmp(sym + 8, name)) ||
> 		(!strncmp(sym, "__arm64_compat_", 15) && !strcmp(sym + 15, name));
> 
> Do we need to handle compat (i.e. 32-bit) tasks here?

Only if you want to trace compat syscalls as well ;-)

-- Steve