linux-kernel - Re: [PATCH] locktorture: Fix Oops when reader/writer count is 0

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: <20171109164520.GD3624@linux.vnet.ibm.com>
Date:   Thu, 9 Nov 2017 08:45:20 -0800
From:   "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:     Davidlohr Bueso <dave@...olabs.net>
Cc:     Peter Zijlstra <peterz@...radead.org>,
        Jeremy Linton <jeremy.linton@....com>,
        linux-kernel@...r.kernel.org, mingo@...hat.com,
        josh@...htriplett.org
Subject: Re: [PATCH] locktorture: Fix Oops when reader/writer count is 0

On Thu, Nov 09, 2017 at 08:19:25AM -0800, Davidlohr Bueso wrote:
> On Wed, 08 Nov 2017, Paul E. McKenney wrote:
> 
> >Jeremy, could you please test Dave's patches and make sure that they
> >work for you?  That way I can apply your Tested-by.  Dave, any objection
> >to my adding Jeremy's Reported-by to your /201 patch?
> 
> No, feel free.

Applied and pushed, thank you both!

							Thanx, Paul