linux-kernel - Re: [PATCH v3 2/4] tracing: Make 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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 24 Aug 2009 10:40:25 +0900
From:	Paul Mundt <lethal@...ux-sh.org>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	Josh Stone <jistone@...hat.com>, linux-kernel@...r.kernel.org,
	Jason Baron <jbaron@...hat.com>, Ingo Molnar <mingo@...e.hu>,
	Li Zefan <lizf@...fujitsu.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
	Jiaying Zhang <jiayingz@...gle.com>,
	Martin Bligh <mbligh@...gle.com>,
	Lai Jiangshan <laijs@...fujitsu.com>
Subject: Re: [PATCH v3 2/4] tracing: Make syscall_(un)regfunc arch-specific

On Sun, Aug 23, 2009 at 11:14:24PM +0200, Frederic Weisbecker wrote:
> On Fri, Aug 21, 2009 at 09:58:43PM -0700, Josh Stone wrote:
> > The bodies of syscall_regfunc and syscall_unregfunc need the
> > arch-specific flag TIF_SYSCALL_TRACEPOINT, which only exists
> > on x86 and s390, so they should live in arch-specific files.
> 
> Sh also does, but currently in a seperate development branch.
> (Adding Paul Mundt in Cc to prevent from further linux-next breakage).
> 
Thanks, I'll take care of this as well as the other ftrace syscalls
breakage during the merge window. At the moment I don't have any good
ideas on how to fix the workflow issues, and -tip likewise doesn't care
about -next impact, so there's somewhat of an impasse.
--
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/