On Fri, Apr 07, 2017 at 06:05:02PM +0200, David Sterba wrote: > 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 <rdunlap@xxxxxxxxxxxxx> > > > > > > > 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 / . Fixed and updated for-next pushed to my k.org repository. -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
