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, 4 Aug 2016 15:36:05 +0200
From:	Geert Uytterhoeven <geert@...ux-m68k.org>
To:	George Spelvin <linux@...encehorizons.net>
Cc:	Arnd Bergmann <arnd@...db.de>,
	kernel-build-reports@...ts.linaro.org, bot@...nelci.org,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: next build: 143 builds: 1 failed, 142 passed, 1 error, 22
 warnings (next-20160801)

Hi George,

On Mon, Aug 1, 2016 at 4:57 PM, George Spelvin
<linux@...encehorizons.net> wrote:
> Arnd Bergmann <arnd@...db.de> wrote:
>>> Warnings:
>>>     lib/test_hash.c:224:7: warning: "HAVE_ARCH__HASH_32" is not defined [-Wundef]
>>>     lib/test_hash.c:229:7: warning: "HAVE_ARCH_HASH_32" is not defined [-Wundef]
>>>     lib/test_hash.c:234:7: warning: "HAVE_ARCH_HASH_64" is not defined [-Wundef]
>>>     lib/test_hash.c:146:2: warning: missing braces around initializer [-Wmissing-braces]
>>>     lib/test_hash.c:146:2: warning: (near initialization for 'hash_or[0]') [-Wmissing-braces]
>
>> Upgrading to gcc-4.9 will fix avoid that, and a couple of workarounds have
>> been discussed before, but I don't know why none of them got merged.
>
> Geert Uytterhoeven was the first to find this problem and propose a
> patch, which I acked, and thought it was going in via the m68k tree.
> Helge Deller did the same a couple days later, and I told him not to
> bother because Geert had taken care of it.
>
> Here are the patches:
> https://marc.info/?l=linux-kernel&m=146454366031110
> https://marc.info/?l=linux-kernel&m=146454366131111
>
> Perhaps there was some confusion about whose version was going in, or
> via which tree.  Maybe I was wrong to assume Geert was putting them in
> the m68k tree.

As these patches were meant for generic non-m68k code, I didn't plan
to take them
through my tree.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ