From: Joe Perches <joe@perches.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Zach Brown <zab@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Andreas Schwab <schwab@linux-m68k.org>,
Josef Bacik <jbacik@fusionio.com>, Thorsten Glaser <tg@mirbsd.de>,
Debian GNU/Linux m68k <debian-68k@lists.debian.org>,
linux-btrfs@vger.kernel.org,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
David Woodhouse <David.Woodhouse@intel.com>,
Chris Mason <chris.mason@fusionio.com>,
scsi <linux-scsi@vger.kernel.org>
Subject: Re: btrfs zero divide
Date: Wed, 14 Aug 2013 11:07:46 -0700 [thread overview]
Message-ID: <1376503665.1949.98.camel@joe-AO722> (raw)
In-Reply-To: <CAMuHMdV-nBbhKbVSAAwh5M45-7kz4RJRqfHrCfudRA5dE2CKoA@mail.gmail.com>
On Wed, 2013-08-14 at 10:56 +0200, Geert Uytterhoeven wrote:
> These bring in the 64-bit divisor from somewhere else, so they're less
> trivial to fix.
Using div64_u64 or div64_s64 could fix it.
Maybe that could be added to do_div too.
prev parent reply other threads:[~2013-08-14 18:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.BSM.4.64L.1307300820160.20675@herc.mirbsd.org>
2013-07-30 9:07 ` btrfs zero divide (was: Re: Linux 3.10 problem reports (yes, plural)) Geert Uytterhoeven
2013-07-30 15:40 ` btrfs zero divide Thorsten Glaser
2013-07-30 17:13 ` btrfs zero divide (was: Re: Linux 3.10 problem reports (yes, plural)) Josef Bacik
2013-07-30 17:36 ` Joe Perches
2013-07-30 19:02 ` btrfs zero divide Thorsten Glaser
2013-07-30 20:40 ` Josef Bacik
2013-07-30 21:05 ` Joe Perches
2013-07-30 21:25 ` Thorsten Glaser
2013-08-08 20:01 ` Thorsten Glaser
2013-08-09 12:26 ` Andreas Schwab
2013-08-09 12:30 ` Andreas Schwab
2013-08-09 14:35 ` Josef Bacik
2013-08-13 12:12 ` Geert Uytterhoeven
2013-08-09 18:04 ` Zach Brown
2013-08-13 16:32 ` Geert Uytterhoeven
2013-08-14 8:40 ` Geert Uytterhoeven
2013-08-14 8:56 ` Geert Uytterhoeven
2013-08-14 18:07 ` Joe Perches [this message]
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=1376503665.1949.98.camel@joe-AO722 \
--to=joe@perches.com \
--cc=David.Woodhouse@intel.com \
--cc=akpm@linux-foundation.org \
--cc=chris.mason@fusionio.com \
--cc=debian-68k@lists.debian.org \
--cc=geert@linux-m68k.org \
--cc=jbacik@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=schwab@linux-m68k.org \
--cc=tg@mirbsd.de \
--cc=zab@redhat.com \
/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).