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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Mon, 10 Nov 2014 14:17:48 -0800
From:	Guenter Roeck <>
To:	Stephen Rothwell <>
Subject: Re: linux-next: Tree for Nov 10

On Mon, Nov 10, 2014 at 08:59:45PM +1100, Stephen Rothwell wrote:
> Hi all,
> Changes since 20141106:
> New tree: nios2
> The slave-dma tree gained a build failure so I used the version from
> next-20141106.
> The mmc-uh tree gained a conflict against the arm-soc tree.
> The tiny tree gained conflicts against Linus' and the net-next trees.
> The driver-core tree gained conflicts against the pm, mfd, l2-mtd,
> sound-asoc and wireless-next trees.
> The tty tree gained conflicts against the tip and tty.current trees.
> The usb-gadget tree gained a conflict against the driver-core tree.
> The char-misc tree gained a conflict agsinst the staging tree.
> The scsi tree gained a build failure so I used teh version from
> next-20141106.
> The pinctrl tree gained conflicts against the arm-soc and driver-core
> trees.
> The tiny tree gained a build failure for which I reverted a commit.
> The akpm-current tree gained conflicts against the driver-core and tiny
> trees and still had its build failures for which I applied two patches.
> Non-merge commits (relative to Linus' tree): 5350
>  5611 files changed, 164785 insertions(+), 151258 deletions(-)
Build results:
	total: 133 pass: 129 fail: 4
Failed builds:

Qemu tests:
	total: 30 pass: 29 fail: 1
Failed tests:



In file included from ./arch/hexagon/include/asm/io.h:33:0,
                 from include/linux/io.h:22,
                 from include/linux/irq.h:23,
                 from include/asm-generic/hardirq.h:12,
                 from arch/hexagon/include/generated/asm/hardirq.h:1,
                 from include/linux/hardirq.h:8,
                 from include/linux/memcontrol.h:24,
                 from include/linux/swap.h:8,
                 from ./arch/hexagon/include/asm/pgtable.h:27,
                 from include/linux/mm.h:52,
                 from arch/hexagon/kernel/asm-offsets.c:28:
./arch/hexagon/include/asm/cacheflush.h: In function 'copy_to_user_page':
./arch/hexagon/include/asm/cacheflush.h:89:22: error: 'VM_EXEC' undeclared (first use in this function)
./arch/hexagon/include/asm/cacheflush.h:89:22: note: each undeclared identifier is reported only once for each function it appears in
make[1]: *** [arch/hexagon/kernel/asm-offsets.s] Error 1
make: *** [prepare0] Error 2


In file included from ./arch/sparc/include/asm/pgtable.h:4:0,
                 from include/linux/mm.h:52,
                 from include/linux/pid_namespace.h:6,
                 from include/linux/ptrace.h:8,
                 from include/linux/ftrace.h:13,
                 from include/linux/init_task.h:8,
                 from init/init_task.c:1:
./arch/sparc/include/asm/pgtable_64.h: In function 'pmd_dirty':
./arch/sparc/include/asm/pgtable_64.h:674:2: error: incompatible types when returning type 'long unsigned int' but 'pmd_t' was expected


drivers/tty/vt/vt.c: In function 'tioclinux':
drivers/tty/vt/vt.c:2703:4: error: implicit declaration of function
'vt_get_kmsg_redirect' [-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
make[3]: *** [drivers/tty/vt/vt.o] Error 1


arch/arm/plat-orion/gpio.c: In function 'orion_gpio_unmask_irq':
arch/arm/plat-orion/gpio.c:509:2: error: too few arguments to function

and many similar follow-up errors.


Stalls until killed. There are several messages such as
	Driver 'serial' needs an owner
in the log.


Details at

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists