From: Joe Perches <joe@perches.com>
To: Josef Bacik <jbacik@fusionio.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
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>
Subject: Re: btrfs zero divide (was: Re: Linux 3.10 problem reports (yes, plural))
Date: Tue, 30 Jul 2013 10:36:10 -0700 [thread overview]
Message-ID: <1375205770.2075.121.camel@joe-AO722> (raw)
In-Reply-To: <20130730171329.GF24583@localhost.localdomain>
On Tue, 2013-07-30 at 13:13 -0400, Josef Bacik wrote:
> I've looked at all the places we do divides in this function and it
> doesn't look like we're doing this anywhere but I could be blind,
do_div seems a likely suspect...
/*
* stripe_nr counts the total number of stripes we have to stride
* to get to this block
*/
do_div(stripe_nr, stripe_len);
next prev parent reply other threads:[~2013-07-30 17:36 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 [this message]
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
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=1375205770.2075.121.camel@joe-AO722 \
--to=joe@perches.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=tg@mirbsd.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.