From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Sterba Subject: Re: linux-next: Tree for Apr 7 (btrfs) Date: Fri, 7 Apr 2017 18:05:02 +0200 Message-ID: <20170407160502.GV4781@twin.jikos.cz> References: <20170407182732.455c5c90@canb.auug.org.au> <3f143e53-652b-8690-d71c-dae42ab14a09@infradead.org> Reply-To: dsterba@suse.cz Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mx2.suse.de ([195.135.220.15]:57267 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754148AbdDGQFF (ORCPT ); Fri, 7 Apr 2017 12:05:05 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-next-owner@vger.kernel.org List-ID: To: Randy Dunlap Cc: Stephen Rothwell , Linux-Next Mailing List , Linux Kernel Mailing List , linux-btrfs@vger.kernel.org On Fri, Apr 07, 2017 at 08:10:48AM -0700, Randy Dunlap wrote: > On 04/07/17 08:08, Randy Dunlap wrote: > > On 04/07/17 01:27, Stephen Rothwell wrote: > >> Hi all, > >> > >> Changes since 20170406: > >> > > > > on i386: > > > > ERROR: "__udivdi3" [fs/btrfs/btrfs.ko] undefined! > > > > Reported-by: Randy Dunlap > > > > or when built-in: > > fs/built-in.o: In function `scrub_bio_end_io_worker': > scrub.c:(.text+0x3d1908): undefined reference to `__udivdi3' > fs/built-in.o: In function `scrub_raid56_parity': > scrub.c:(.text+0x3d23cc): undefined reference to `__udivdi3' > scrub.c:(.text+0x3d3342): undefined reference to `__udivdi3' > scrub.c:(.text+0x3d3755): undefined reference to `__udivdi3' Sorry, I can't reproduce it here, I've also tried my other for-next snapshot branches, same. We have some recent patches that could trigger the __udivdi3 build check, "Btrfs: update scrub_parity to use u64 stripe_len" (7d0ef8b4dbbd22) manual check or with help of coccinell didn't show me any instances of 64bit division with / .