From: Rabin Vincent <rabin.vincent@axis.com>
To: linux@armlinux.org.uk
Cc: rostedt@goodmis.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Rabin Vincent <rabinv@axis.com>
Subject: [PATCH] ARM: ftrace: fix syscall name matching
Date: Mon, 14 Nov 2016 14:03:45 +0100 [thread overview]
Message-ID: <1479128625-20948-1-git-send-email-rabin.vincent@axis.com> (raw)
From: Rabin Vincent <rabinv@axis.com>
ARM has a few system calls (most notably mmap) for which the names of
the functions which are referenced in the syscall table do not match the
names of the syscall tracepoints. As a consequence of this, these
tracepoints are not made available. Implement
arch_syscall_match_sym_name to fix this and allow tracing even these
system calls.
Signed-off-by: Rabin Vincent <rabinv@axis.com>
---
arch/arm/include/asm/ftrace.h | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
diff --git a/arch/arm/include/asm/ftrace.h b/arch/arm/include/asm/ftrace.h
index bfe2a2f..8467909 100644
--- a/arch/arm/include/asm/ftrace.h
+++ b/arch/arm/include/asm/ftrace.h
@@ -54,6 +54,27 @@ static inline void *return_address(unsigned int level)
#define ftrace_return_address(n) return_address(n)
+#define ARCH_HAS_SYSCALL_MATCH_SYM_NAME
+
+static inline bool arch_syscall_match_sym_name(const char *sym,
+ const char *name)
+{
+ /* Skip sys_ */
+ sym += 4;
+ name += 4;
+
+ if (!strcmp(sym, "mmap2"))
+ sym = "mmap_pgoff";
+ else if (!strcmp(sym, "statfs64_wrapper"))
+ sym = "statfs64";
+ else if (!strcmp(sym, "fstatfs64_wrapper"))
+ sym = "fstatfs64";
+ else if (!strcmp(sym, "arm_fadvise64_64"))
+ sym = "fadvise64_64";
+
+ return !strcmp(sym, name);
+}
+
#endif /* ifndef __ASSEMBLY__ */
#endif /* _ASM_ARM_FTRACE */
--
2.1.4
next reply other threads:[~2016-11-14 13:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 13:03 Rabin Vincent [this message]
2016-11-14 13:40 ` [PATCH] ARM: ftrace: fix syscall name matching Russell King - ARM Linux
2016-11-14 15:40 ` Steven Rostedt
2016-11-14 15:44 ` Steven Rostedt
2016-11-15 15:18 ` Rabin Vincent
2016-11-15 10:17 ` [PATCHv2] " Rabin Vincent
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1479128625-20948-1-git-send-email-rabin.vincent@axis.com \
--to=rabin.vincent@axis.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=rabinv@axis.com \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).