linux-kernel - Re: [PATCH][next] ftrace: Fix -Wcast-function-type warnings on powerpc64

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:   Tue, 12 Oct 2021 22:44:45 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     "Gustavo A. R. Silva" <gustavoars@...nel.org>
Cc:     Ingo Molnar <mingo@...hat.com>,
        Daniel Bristot de Oliveira <bristot@...nel.org>,
        linux-kernel@...r.kernel.org, Jann Horn <jannh@...gle.com>
Subject: Re: [PATCH][next] ftrace: Fix -Wcast-function-type warnings on
 powerpc64

On Tue, 12 Oct 2021 21:39:20 -0500
"Gustavo A. R. Silva" <gustavoars@...nel.org> wrote:

> On Tue, Oct 12, 2021 at 10:23:40PM -0400, Steven Rostedt wrote:
> > On Tue, 12 Oct 2021 20:40:42 -0500
> > "Gustavo A. R. Silva" <gustavoars@...nel.org> wrote:
> >   
> > > Do you mind if, in the meantime, I add your patch to my -next tree?
> > > So, I can enable -Wcast-function-type in linux-next --I want to get
> > > ready for the next merge window.  
> > 
> > You mean to push it to Linus as well? I'm not sure that's the best way.  
> 
> No. Just add it to my -next tree, temporarily. So, I can enable the
> compiler option and it can be tested in linux-next (and no more of
> these issues are introduced). The only part I'll send to Linus would
> be the Makefile patch.

Sure, I have no problem with that.

> 
> > I'm still working on some bugs that are going to go into this rc
> > release, and then I plan on pushing my for-next queue (which includes
> > this change).  
> 
> Once you have it ready, I would remove it from my tree.

Sounds like a plan ;-)

-- Steve