linux-kernel - Re: [PATCH 1/1] ftrace: fix dynamic ftrace filter reset issue

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]

Message-ID: <CA+jqyFD7bq1jSNG9QV+iQx-PGsOmjSAyzo-pjLFau96ei=xNGA@mail.gmail.com>
Date:	Tue, 27 Mar 2012 09:21:51 +0530
From:	Rajesh Bhagat <rajesh.lnx@...il.com>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Frederic Weisbecker <fweisbec@...il.com>,
	Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] ftrace: fix dynamic ftrace filter reset issue

Hi Steven,

Thanks for your feedback.
I will work on the V2 of this patch to get the mentioned issue resolved.

- Rajesh


On Mon, Mar 26, 2012 at 11:15 PM, Steven Rostedt <rostedt@...dmis.org> wrote:
> On Sat, 2012-03-24 at 09:55 -0400, Steven Rostedt wrote:
>
>> That said, I may consider taking the patch, as another way of resetting
>> the tracer. I have to see what workflows it will affect first.
>
> This is what I was afraid of. The tracers irqsoff and preemptoff do not
> get reset if you echo the tracer name into the current_tracer. This
> makes different tracers inconsistent.
>
> All tracers must act the same. So, it's a no go for this patch, at least
> in its current form.
>
> -- 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/