linux-kernel - Re: linux-next: build failure after merge of the net-next tree

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:	Tue, 17 Dec 2013 21:21:45 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	sfr@...b.auug.org.au
Cc:	netdev@...r.kernel.org, linux-next@...r.kernel.org,
	linux-kernel@...r.kernel.org, ffusco@...hat.com,
	dborkman@...hat.com, tgraf@...hat.com
Subject: Re: linux-next: build failure after merge of the net-next tree

From: Stephen Rothwell <sfr@...b.auug.org.au>
Date: Wed, 18 Dec 2013 12:56:43 +1100

> After merging the net-next tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
> 
> In file included from include/linux/hashtable.h:12:0,
>                  from include/linux/elevator.h:5,
>                  from include/linux/blkdev.h:222,
>                  from init/do_mounts.h:2,
>                  from init/do_mounts_rd.c:21:
> include/linux/hash.h:18:22: fatal error: asm/hash.h: No such file or directory
>  #include <asm/hash.h>
>                       ^
> 
> And many more ...
> 
> Caused by commit 71ae8aac3e19 ("lib: introduce arch optimized hash
> library").  Presumably this would break any architecture other than
> x86 :-(

The author believed that putting a header file in asm-generic/
makes it get used automatically by architectures which lack
that header file.

At the very least we have to add a generic-y entry for it to
arch/${ARCH}/include/asm/Kbuild

I'll try to fix this up, thanks for the report.
--
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/