linux-kernel - Re: [PATCH v1] tracing: Drop static keyword for exported ftrace_set_clr

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: <20190904061910.4f9462d3@oasis.local.home>
Date:   Wed, 4 Sep 2019 06:19:10 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc:     Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
        Divya Indi <divya.indi@...cle.com>
Subject: Re: [PATCH v1] tracing: Drop static keyword for exported
 ftrace_set_clr_event()

On Mon, 2 Sep 2019 12:34:06 +0300
Andy Shevchenko <andriy.shevchenko@...ux.intel.com> wrote:

> On Fri, Aug 30, 2019 at 05:04:24PM -0400, Steven Rostedt wrote:
> > On Fri, 30 Aug 2019 22:32:28 +0300
> > Andy Shevchenko <andriy.shevchenko@...ux.intel.com> wrote:
> >   
> > > When we export something, it shan't be static.  
> > 
> > I'm finally getting around to my patch queue (it's unfortunately much
> > bigger than I should be). But my punishment is duplicate patches.
> > 
> > Someone beat you to it...
> > 
> >  http://lkml.kernel.org/r/20190704172110.27041-1-efremov@linux.com  
> 
> Looking to the original patch and taking into account that there is no user for
> it, I guess the best option to simple revert original one (it will clean up
> export table).
> 

Except there will be.

 http://lkml.kernel.org/r/1565805327-579-1-git-send-email-divya.indi@oracle.com


-- Steve