linux-kernel - Re: [for-next][PATCH 09/18] tracing: Move pipe reference to trace array instead of current

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]

Message-ID: <20200731171626.2c51e818@oasis.local.home>
Date:   Fri, 31 Jul 2020 17:16:26 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     dann frazier <dann.frazier@...onical.com>
Cc:     linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...nel.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Ian May <ian.may@...onical.com>
Subject: Re: [for-next][PATCH 09/18] tracing: Move pipe reference to trace
 array instead of current_tracer

On Fri, 31 Jul 2020 13:33:45 -0600
dann frazier <dann.frazier@...onical.com> wrote:

> > This is marked as "Fixes" but is more of a clean up than a true fix.
> > Backport if you want, but its not critical.  
> 
> Thanks Steven! In case it helps backport consideration, I wanted to
> note that this addresses an issue we've seen with users trying to
> change current_tracer when they happen to have rasdaemon
> installed. rasdaemon uses the trace_pipe interface at runtime, which
> therefore blocks changing the current tracer. But of course, unless
> you know about rasdaemon internals, it isn't exactly an obvious
> failure mode.

Ah, then this should probably be backported.

When I push to Linus (during the next merge window) and it gets into
Linus's tree. Feel free to send stable@...r.kernel.org the sha1 of this
commit, and ask for it to be backported for the above stated reason.

-- Steve