linux-kernel - Re: linux-next: build failure after merge of the final tree (nfsd tree related)

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: <20130403113301.GA13951@fieldses.org>
Date:	Wed, 3 Apr 2013 07:33:01 -0400
From:	"J. Bruce Fields" <bfields@...ldses.org>
To:	Jeff Layton <jlayton@...hat.com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (nfsd
 tree related)

On Wed, Apr 03, 2013 at 07:10:54AM -0400, Jeff Layton wrote:
> On Wed, 3 Apr 2013 17:42:19 +1100
> Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> 
> > Hi all,
> > 
> > After merging the final tree, today's linux-next build (arm defconfig)
> > failed like this:
> > 
> > fs/built-in.o: In function `nfsd_reply_cache_stats_show':
> > super.c:(.text+0x87308): undefined reference to `__udivdi3'
> > 
> > Probably caused by commit 187da2f90879 ("nfsd: keep track of the max and
> > average time to search the cache") which adds a divide by u64
> > (num_searches).
> > 
> > I have reverted that commit and the following one for today.
> 
> Thanks, known problem...
> 
> Looks like Bruce's tree has an older version of that patch series. I
> think we just need to get him to drop that one and merge the new one.

Arrgh, sorry--could you remind me which is the new one?

--b.
--
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/