From: Joe Perches <joe@perches.com>
To: Josef Bacik <jbacik@fusionio.com>
Cc: Thorsten Glaser <tg@mirbsd.de>,
Geert Uytterhoeven <geert@linux-m68k.org>,
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
Date: Tue, 30 Jul 2013 14:05:47 -0700 [thread overview]
Message-ID: <1375218347.2075.133.camel@joe-AO722> (raw)
In-Reply-To: <20130730204001.GG24583@localhost.localdomain>
On Tue, 2013-07-30 at 16:40 -0400, Josef Bacik wrote:
> So stripe_len shouldn't be 0, if it is you have bigger problems :). Is this a
> corrupt fs or something? If there was some sort of corruption that occured then
> I suppose stripe_len could be 0 and we'd need to catch that somewhere higher up
> the stack and error out. Is there a way you could check and see if that's the
> case? Thanks,
Maybe use a temporary check in do_div
Something like this maybe. (uncompiled/untested)
---
include/asm-generic/div64.h | 43 +++++++++++++++++++++++++++++--------------
1 file changed, 29 insertions(+), 14 deletions(-)
diff --git a/include/asm-generic/div64.h b/include/asm-generic/div64.h
index 8f4e319..cce75fe 100644
--- a/include/asm-generic/div64.h
+++ b/include/asm-generic/div64.h
@@ -19,16 +19,25 @@
#include <linux/types.h>
#include <linux/compiler.h>
+#include <linux/bug.h>
+#include <linux/printk.h>
#if BITS_PER_LONG == 64
-# define do_div(n,base) ({ \
+# define do_div(n, base) \
+({ \
uint32_t __base = (base); \
uint32_t __rem; \
- __rem = ((uint64_t)(n)) % __base; \
- (n) = ((uint64_t)(n)) / __base; \
+ if (__base == 0) { \
+ WARN(1, "Attempted division by 0\n"); \
+ dump_stack(); \
+ __rem = 0; \
+ } else { \
+ __rem = ((uint64_t)(n)) % __base; \
+ (n) = ((uint64_t)(n)) / __base; \
+ } \
__rem; \
- })
+})
#elif BITS_PER_LONG == 32
@@ -37,16 +46,22 @@ extern uint32_t __div64_32(uint64_t *dividend, uint32_t divisor);
/* The unnecessary pointer compare is there
* to check for type safety (n must be 64bit)
*/
-# define do_div(n,base) ({ \
- uint32_t __base = (base); \
- uint32_t __rem; \
- (void)(((typeof((n)) *)0) == ((uint64_t *)0)); \
- if (likely(((n) >> 32) == 0)) { \
- __rem = (uint32_t)(n) % __base; \
- (n) = (uint32_t)(n) / __base; \
- } else \
- __rem = __div64_32(&(n), __base); \
- __rem; \
+# define do_div(n, base) \
+({ \
+ uint32_t __base = (base); \
+ uint32_t __rem; \
+ (void)(((typeof((n)) *)0) == ((uint64_t *)0)); \
+ if (__base == 0) { \
+ WARN(1, "Attempted division by 0\n"); \
+ dump_stack(); \
+ __rem = 0; \
+ } else if (likely(((n) >> 32) == 0)) { \
+ __rem = (uint32_t)(n) % __base; \
+ (n) = (uint32_t)(n) / __base; \
+ } else { \
+ __rem = __div64_32(&(n), __base); \
+ } \
+ __rem; \
})
#else /* BITS_PER_LONG == ?? */
next prev parent reply other threads:[~2013-07-30 21:05 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 [this message]
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=1375218347.2075.133.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 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).