netdev - Re: arm64 allmodconfig failures in nft_reject

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, 13 Nov 2014 14:35:13 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	pablo@...filter.org
Cc:	broonie@...nel.org, linux@...ck-us.net, kaber@...sh.net,
	kadlec@...ckhole.kfki.hu, stephen@...workplumber.org,
	linaro-kernel@...ts.linaro.org,
	kernel-build-reports@...ts.linaro.org,
	netfilter-devel@...r.kernel.org, coreteam@...filter.org,
	bridge@...ts.linux-foundation.org, netdev@...r.kernel.org
Subject: Re: arm64 allmodconfig failures in nft_reject_bridge.c

From: Pablo Neira Ayuso <pablo@...filter.org>
Date: Thu, 13 Nov 2014 12:43:57 +0100

> On Thu, Nov 13, 2014 at 11:33:20AM +0000, Mark Brown wrote:
>> Since about -rc3 we've been seeing build failures in Linus' tree on
>> arm64 allmodconfig due to:
>> 
>> > 	arm64-allmodconfig
>> > ../net/bridge/netfilter/nft_reject_bridge.c:240:3: error: implicit declaration of function 'csum_ipv6_magic' [-Werror=implicit-function-declaration]
>> 
>> By the time I looked into this it was fixed in -next by c1207c049b204b0
>> (netfilter: nft_reject_bridge: Fix powerpc build error) from Guenter but
>> that doesn't seem to have made it into -rc4 so I just wanted to check
>> that this fix was intended to go to Linus before v3.18?
> 
> I can see this in David's tree:
> 
> http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=c1207c049b204b0a96535dc5416aee331b51e0e1
> 
> I think this was reported by when -rc4 was already out, so you'll see
> this by -rc5.

I hold changes in my tree for a week or more, because I want them to
"cook" there before they go to Linus.

So if it takes a week or two for a bug fix like this to propagate into
Linus's tree, that's just what sometimes happens.

In the mean time you can apply the fix locally if you absolutely have
to have it right at this moment, that is the freedom that everyone
has.

FWIW, I plan to push my tree to Linus some time today, so this will be
resolved in the next day or so.

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html