linux-kernel - Re: [PATCH 04/11] tracing: fix disabling of soft 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] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 21 Jun 2013 16:39:31 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
Cc:	Tom Zanussi <tom.zanussi@...ux.intel.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 04/11] tracing: fix disabling of soft disable

On Fri, 2013-06-21 at 20:12 +0900, Masami Hiramatsu wrote:
> (2013/06/21 3:31), Tom Zanussi wrote:
> > The comment on the soft disable 'disable' case of
> > __ftrace_event_enable_disable() states that the soft disable bit
> > should be cleared in that case, but currently only the soft mode bit
> > is actually cleared.
> > 
> > This essentially leaves the standard non-soft-enable enable/disable
> > paths as the only way to clear the soft disable flag, but the soft
> > disable bit should also be cleared when removing a trigger with '!'.
> 
> Indeed, the soft-disabled flag may remain after the event itself
> disabled. However that soft-disabled flag will be cleared when
> the event is re-enabled. it seems no bad side-effect.
> 
> Thus I doubt this patch is separately required. I guess this is
> required for adding new trigger flag, isn't it? :)

Tom, I'm guessing Masami is correct here. It's needed for the trigger
work to work, correct?

Either way, I probably could add it as a clean up patch regardless. I'll
just have to test the hell out of it some more, as the accounting for
soft-disable vs real disable was a PITA.

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