linux-kernel - Re: [PATCH 3/3] tracing: Remove leftover FTRACE_ENABLE/DISABLE

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] [day] [month] [year] [list]

Date:	Wed, 15 Sep 2010 12:21:26 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Valdis.Kletnieks@...edu
Cc:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 3/3] tracing: Remove leftover
 FTRACE_ENABLE/DISABLE_MCOUNT enums

On Wed, 2010-09-15 at 12:10 -0400, Valdis.Kletnieks@...edu wrote:
> On Tue, 14 Sep 2010 23:01:42 EDT, Steven Rostedt said:
> > From: Steven Rostedt <srostedt@...hat.com>
> > 
> > The enums for FTRACE_ENABLE_MCOUNT and FTRACE_DISABLE_MCOUNT were
> > used as commands to ftrace_run_update_code(). But these commands
> > were used by the old nasty ftrace daemon that has long been slain.
> 
> > -	FTRACE_START_FUNC_RET		= (1 << 5),
> > -	FTRACE_STOP_FUNC_RET		= (1 << 6),
> > +	FTRACE_START_FUNC_RET		= (1 << 3),
> > +	FTRACE_STOP_FUNC_RET		= (1 << 4),
> 
> This renumber isn't visible to user space, correct? (Asking because the enable/
> disable apparently *were* visible to the since-slain userspace daemon)

Nope, it's not visible to userspace, and the slain-daemon was a kernel
thread, not userspace.

-- Steve


--
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/