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:	Thu, 26 Jan 2012 13:43:33 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	geert@...ux-m68k.org
Cc:	rdunlap@...otime.net, sfr@...b.auug.org.au,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	gleb@...hat.com, netdev@...r.kernel.org, glommer@...allels.com
Subject: Re: linux-next: Tree for Jan 25 (net/sock.h, jump_label, memcg)

From: Geert Uytterhoeven <geert@...ux-m68k.org>
Date: Thu, 26 Jan 2012 18:18:28 +0100

> On Wed, Jan 25, 2012 at 20:07, Randy Dunlap <rdunlap@...otime.net> wrote:
>> back to net/sock.h and jump_label:
>>
>> (on i386:)
>>
>> /next/linux-next-20120125/include/net/sock.h:953:2: error: implicit declaration of function 'static_branch'
>> /next/linux-next-20120125/include/linux/jump_label.h:43:29: error: conflicting types for 'static_branch'
>>
>> Full randconfig file is attached.
> 
> Without having to add randomness, also in m68k/allmodconfig, now in Linus'
> tree :-(
> http://kisskb.ellerman.id.au/kisskb/buildresult/5491860/

Glauber are you actually going to fix this or are you going to ignore
this bug report for another couple days?!?!

Frankly, I'm so sick and tired of all of these socket mem cgroup
regressions, this is way out of control and every "fix" seems to add
more build or runtime regressions.

Glauber, this has to stabilize soon or I will revert every single one
of your changes, and it will take a nuclear war and a multi-month
audit of your code to get those changes into the tree again.

--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ