linux-kernel - Re: [RFC][PATCH 0/7] kref improvements

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: <20161115150519.GA21257@kroah.com>
Date:   Tue, 15 Nov 2016 16:05:19 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Ingo Molnar <mingo@...nel.org>
Cc:     Peter Zijlstra <peterz@...radead.org>, keescook@...omium.org,
        will.deacon@....com, elena.reshetova@...el.com, arnd@...db.de,
        tglx@...utronix.de, hpa@...or.com, dave@...gbits.org,
        linux-kernel@...r.kernel.org
Subject: Re: [RFC][PATCH 0/7] kref improvements

On Tue, Nov 15, 2016 at 08:42:45AM +0100, Ingo Molnar wrote:
> * Greg KH <gregkh@...uxfoundation.org> wrote:
> > On Mon, Nov 14, 2016 at 06:39:46PM +0100, Peter Zijlstra wrote:
> > Thanks so much for doing these, at the very least, I want to take the
> > kref-abuse-fixes now as those users shouldn't be doing those foolish
> > things.  Any objection for me taking some of them through my tree now?
> 
> Very nice series indeed!
> 
> We normally route atomics related patches through tip:locking/core (there's also 
> tip:atomic/core), but this is a special case I think, given how broadly it 
> interacts with driver code.
> 
> So both would work I think: we could concentrate these and only these patches into 
> tip:atomic/core into an append-only tree, or you can carry them in the driver tree 
> - whichever variant you prefer!

I have no objection for them going through a tip:whataver tree/branch,
if you all want to do that, it makes it easier for me :)

I'm guessing another series will come out before they get merged there,
so I'll hold off on providing an Acked-by: until then.

thanks,

greg k-h