From: David Sterba <dsterba@suse.cz>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-btrfs@vger.kernel.org
Subject: Re: linux-next: Tree for Apr 7 (btrfs)
Date: Fri, 7 Apr 2017 18:05:02 +0200 [thread overview]
Message-ID: <20170407160502.GV4781@twin.jikos.cz> (raw)
In-Reply-To: <b8b42950-e775-398d-1364-8bb7c117aa12@infradead.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 <rdunlap@infradead.org>
> >
>
> 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 / .
next prev parent reply other threads:[~2017-04-07 16:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 8:27 linux-next: Tree for Apr 7 Stephen Rothwell
2017-04-07 15:08 ` linux-next: Tree for Apr 7 (btrfs) Randy Dunlap
2017-04-07 15:10 ` Randy Dunlap
2017-04-07 16:05 ` David Sterba [this message]
2017-04-10 11:50 ` David Sterba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170407160502.GV4781@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).