linux-kernel - Re: linux-next: Tree for Sep 19

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]

Message-ID: <20140919202410.GA26329@roeck-us.net>
Date:	Fri, 19 Sep 2014 13:24:10 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Christoph Hellwig <hch@....de>,
	Trond Myklebust <trond.myklebust@...marydata.com>
Subject: Re: linux-next: Tree for Sep 19

On Fri, Sep 19, 2014 at 04:58:17PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20140917:
> 
> The fsl tree still had its build failure so I used the version from
> next-20140917.
> 
> The v4l-dvb tree lost its build failure.
> 
> The security tree gained a conflict against the file-locks tree.
> 
> Non-merge commits (relative to Linus' tree): 6014
>  5488 files changed, 217522 insertions(+), 129375 deletions(-)
> 
> ----------------------------------------------------------------------------
> 
i386:allyesconfig:

fs/built-in.o: In function `bl_map_stripe':
dev.c:(.text+0x3489ab): undefined reference to `__udivdi3'
dev.c:(.text+0x3489ca): undefined reference to `__umoddi3'
dev.c:(.text+0x348a83): undefined reference to `__udivdi3'

i386:allmodconfig:
mips:allmodconfig:

ERROR: "__udivdi3" [fs/nfs/blocklayout/blocklayoutdriver.ko] undefined!
ERROR: "__umoddi3" [fs/nfs/blocklayout/blocklayoutdriver.ko] undefined!

Obviously caused by commit 5c83746a0cf ('pnfs/blocklayout: in-kernel
GETDEVICEINFO XDR parsing') which adds fs/nfs/blocklayout/dev.c.
--
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/