linux-kernel - Re: [GIT PULL] locking tree changes for v3.16

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: <20140605124725.GB1975@gmail.com>
Date:	Thu, 5 Jun 2014 14:47:25 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Davidlohr Bueso <davidlohr@...com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org,
	"Paul E. McKenney" <paulmck@...ibm.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [GIT PULL] locking tree changes for v3.16


* Peter Zijlstra <peterz@...radead.org> wrote:

> On Thu, Jun 05, 2014 at 02:35:12PM +0200, Ingo Molnar wrote:
> > 
> > * Peter Zijlstra <peterz@...radead.org> wrote:
> > 
> > > On Thu, Jun 05, 2014 at 01:11:10PM +0200, Ingo Molnar wrote:
> > > > Unfortunately even with the latest bits from you the breakage I 
> > > > reported weeks ago is not resolved:
> > > 
> > > crap, its the qrwlock bits, I fixed it for the config you gave me. 
> > > Some paravirt crap header hell thing. Happen to have another 
> > > .config?
> > 
> > A simple 'make defconfig' triggers the build failure for me:
> > 
> >   kernel/locking/qrwlock.c:24:25: fatal error: asm/qrwlock.h: No such file or directory
> > 
> > If I apply the minimal feature-enabling patch below on top of the base 
> > qrwlock patch.
> > 
> 
> Well, that second patch which you neutered below would've provided that
> asm/qrwlock.h.

Oops, indeed...

> Lemme see if I can find it with randconfig with both patches 
> applied.

I've attached that config to my first report (I've attached it again) 
- it was a !CONFIG_SMP config. If you resolved then please resend the 
latest and I'll check whether there's anything broken.

Thanks,

	Ingo

View attachment "config" of type "text/plain" (101453 bytes)