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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20100122.173618.90816303.davem@davemloft.net>
Date:	Fri, 22 Jan 2010 17:36:18 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	rostedt@...dmis.org
Cc:	vapier@...too.org, linux-kernel@...r.kernel.org,
	fweisbec@...il.com, mingo@...hat.com, brueckner@...ux.vnet.ibm.com,
	heiko.carstens@...ibm.com, lethal@...ux-sh.org
Subject: Re: [PATCH] ftrace: unify arch_syscall_addr() implementations

From: Steven Rostedt <rostedt@...dmis.org>
Date: Fri, 22 Jan 2010 09:36:17 -0500

> [ Added Heiko Carstens and Paul Mundt to Cc ]
> 
> On Fri, 2010-01-22 at 08:43 -0500, Mike Frysinger wrote:
>> also, does the arch_syscall_addr() even really need to be weak ?  or can
>> we assume that everyone is going to be sane and do it the same way ...
>> 
>>  Documentation/trace/ftrace-design.txt |    6 +++++-
>>  arch/s390/kernel/ftrace.c             |   10 ----------
>>  arch/sh/kernel/ftrace.c               |    9 ---------
>>  arch/sparc/kernel/ftrace.c            |   11 -----------
>>  arch/x86/kernel/ftrace.c              |   10 ----------
>>  include/linux/ftrace.h                |    6 ++++++
>>  kernel/trace/trace_syscalls.c         |    6 +++++
> 
> Actually for this patch to be accepted, we need to get the acks from the
> maintainers of s390, sh, and sparc since it touches their code. Doesn't
> matter if it is just removing duplicate code. Still need their acks.

Acked-by: David S. Miller <davem@...emloft.net>
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ