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]
Date:	Tue, 26 Jan 2010 23:50:58 -0500
From:	Mike Frysinger <vapier.adi@...il.com>
To:	rostedt@...dmis.org
Cc:	linux-kernel@...r.kernel.org,
	Frederic Weisbecker <fweisbec@...il.com>,
	Ingo Molnar <mingo@...hat.com>,
	Hendrik Brueckner <brueckner@...ux.vnet.ibm.com>,
	"David S. Miller" <davem@...emloft.net>,
	Heiko Carstens <heiko.carstens@...ibm.com>,
	Paul Mundt <lethal@...ux-sh.org>
Subject: Re: [PATCH] ftrace: unify arch_syscall_addr() implementations

On Fri, Jan 22, 2010 at 09:36, Steven Rostedt wrote:
> On Fri, 2010-01-22 at 08:43 -0500, Mike Frysinger wrote:
>> Every arch_syscall_addr() implementation thus far is the same, so unify
>> them as a default weak in common code so more arches don't have to waste
>> time copying & pasting this simple function.  The Blackfin version is
>> going to be exactly the same.
>>
>> Signed-off-by: Mike Frysinger <vapier@...too.org>
>> ---
>> note: only thing that needs double checking is s390 and sparc where they
>> declared the sys_call_table as an array of ints.  considering this table
>> is supposed to be an array of function pointers, this seems like more of
>> a typo to me ...
>
> I would not be too sure. s390 is very strange, and I would definitely
> want to get an Ack from the arch maintainers first.

i think everyone has checked in with v3 ...
-mike
--
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