linux-kernel - Re: [PATCH tip/core/rcu 0/88] Commits for 4.13

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]

Date:   Fri, 9 Jun 2017 10:57:04 -0700
From:   "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:     Steven Rostedt <rostedt@...dmis.org>
Cc:     linux-kernel@...r.kernel.org, mingo@...nel.org,
        jiangshanlai@...il.com, dipankar@...ibm.com,
        akpm@...ux-foundation.org, mathieu.desnoyers@...icios.com,
        josh@...htriplett.org, tglx@...utronix.de, peterz@...radead.org,
        dhowells@...hat.com, edumazet@...gle.com, fweisbec@...il.com,
        oleg@...hat.com, bobby.prani@...il.com
Subject: Re: [PATCH tip/core/rcu 0/88] Commits for 4.13

On Fri, Jun 09, 2017 at 01:33:31PM -0400, Steven Rostedt wrote:
> On Fri, 9 Jun 2017 10:20:38 -0700
> "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com> wrote:
> 
> 
> > But enough fantasizing about possible futures.  Any thoughts on what
> > could be done to help with this situation in the here and now?
> 
> Unfortunately no, as I don't have enough info to understand all the
> interconnections between the patches to have a better idea on how to
> break them apart.
> 
> But I will say, I've actually written code that would later be removed,
> just to keep things better apart and bisectable.

I have done that as well, but I couldn't see how to get significant
benefit from that with this particular series.

							Thanx, Paul