linux-kernel - Re: [PATCH] uprobes: convert uprobe.ref to refcount

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: <20190211171033.4691d581@gandalf.local.home>
Date:   Mon, 11 Feb 2019 17:10:33 -0500
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Kees Cook <keescook@...omium.org>
Cc:     "Reshetova, Elena" <elena.reshetova@...el.com>,
        Srikar Dronamraju <srikar@...ux.vnet.ibm.com>,
        "peterz@...radead.org" <peterz@...radead.org>,
        "mingo@...hat.com" <mingo@...hat.com>,
        "akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
        "acme@...nel.org" <acme@...nel.org>,
        "alexander.shishkin@...ux.intel.com" 
        <alexander.shishkin@...ux.intel.com>,
        "jolsa@...hat.com" <jolsa@...hat.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] uprobes: convert uprobe.ref to refcount_t

On Mon, 11 Feb 2019 13:49:27 -0800
Kees Cook <keescook@...omium.org> wrote:

> On Mon, Feb 11, 2019 at 12:28 PM Steven Rostedt <rostedt@...dmis.org> wrote:
> >
> > On Mon, 11 Feb 2019 15:27:25 -0500
> > Steven Rostedt <rostedt@...dmis.org> wrote:
> >  
> > > On Mon, 11 Feb 2019 12:21:32 -0800
> > > Kees Cook <keescook@...omium.org> wrote:
> > >  
> > > > > > Looks good to me.
> > > > > >
> > > > > > Reviewed-by: Srikar Dronamraju <srikar@...ux.vnet.ibm.com>  
> > > > >
> > > > > Thank you very much Srikar!
> > > > > Would you be able to take this patch to integration?  
> > > >
> > > > Steve can you pick this up with Srikar's Reviewed-by?  
> > >
> > > Yep. And I'll also add Oleg's acked-by. (Currently doing my "urgent"
> > > patches now).
> > >  
> >
> > Or is this something that can wait till the next merge window?  
> 
> I wouldn't classify the change as _urgent_, no. For "next merge
> window" you mean v5.1, I assume? I think that'd be fine unless Elena
> sees something I don't.

OK, then I'll just place this in the "for-next" branch of mine. Still
need to test what I current have ;-)

-- Steve