linux-kernel - Re: [GIT PULL] locking fixes

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:	Sat, 21 Feb 2015 06:16:53 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [GIT PULL] locking fixes

* Ingo Molnar <mingo@...nel.org> wrote:

> ( I've attached the build log that I saw before sending you 
>   the pull request. )
> 
> The kbuild test robot which tests for warnings didn't 
> report one to me either. I tested a few other configs as 
> well:
> 
>   x86 defconfig (PARAVIRT=n):        0 warnings
>   'make kvmconfig' (PARAVIRT=y):     0 warnings
>   x86 bootable config (attached):    0 warnings

Oh, crap, I just triggered the warnings with:

 x86 defconfig + 'make kvmconfig' + CONFIG_PARAVIRT_SPINLOCKS=y.

My bad, mea culpa ...

I just tested your patch.diff and it fixed the warnings:

  Tested-by: Ingo Molnar <mingo@...nel.org>

Extra sad: I _did_ build and boot test paravirt spinlocks 
as well, but only within a test environment that does not 
show warnings (in general there's too many of them, even 
defconfig is rarely warnings free, although it is with the 
very latest kernel) and my burn-in test before the pull 
request didn't have paravirt spinlocks turned on.

But you do allmodconfig tests and look at warnings so there 
it probably showed up straight away?

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/