linux-kernel - Re: [PATCH v3] ftrace: unify arch_syscall

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: <20100126112929.GA14135@osiris.boeblingen.de.ibm.com>
Date:	Tue, 26 Jan 2010 12:29:29 +0100
From:	Heiko Carstens <heiko.carstens@...ibm.com>
To:	Mike Frysinger <vapier@...too.org>
Cc:	linux-kernel@...r.kernel.org, Steven Rostedt <rostedt@...dmis.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Ingo Molnar <mingo@...hat.com>,
	David Miller <davem@...emloft.net>,
	Paul Mundt <lethal@...ux-sh.org>
Subject: Re: [PATCH v3] ftrace: unify arch_syscall_addr() implementations

On Tue, Jan 26, 2010 at 04:40:03AM -0500, Mike Frysinger wrote:
> Most implementations of arch_syscall_addr() are the same, so create a
> default version in common code and move the one piece that differs (the
> syscall table) to asm/syscall.h.  New arch ports don't have to waste
> time copying & pasting this simple function.
> 
> The s390/sparc versions need to be different, so document why.
> 
> Signed-off-by: Mike Frysinger <vapier@...too.org>
> Acked-by: David S. Miller <davem@...emloft.net>
> Acked-by: Paul Mundt <lethal@...ux-sh.org>
> ---
> v3
> 	- move sys_call_table[] decl to asm/syscall.h
> 	- unify everyone's arch_syscall_addr() again
> 	- mention right tracehook requirements
> 
>  Documentation/trace/ftrace-design.txt |    5 ++---
>  arch/s390/include/asm/syscall.h       |    7 +++++++
>  arch/s390/kernel/ftrace.c             |   10 ----------

Acked-by: Heiko Carstens <heiko.carstens@...ibm.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/