linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fusionio.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: 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 13:13:29 -0400	[thread overview]
Message-ID: <20130730171329.GF24583@localhost.localdomain> (raw)
In-Reply-To: <alpine.DEB.2.02.1307301052010.23107@ayla.of.borg>

On Tue, Jul 30, 2013 at 11:07:30AM +0200, Geert Uytterhoeven wrote:
> On Tue, 30 Jul 2013, Thorsten Glaser wrote:
> > NEW problem: btrfs doesn’t work at all. I had to reboot my
> > buildd into 3.2 using echo s/u/s/o >/proc/sysrq-trigger as
> > the attempt to mount it left the system hanging there.
> 
> > [    0.000000] Linux version 3.10-1-m68k (debian-kernel@lists.debian.org) (gcc version 4.8.1 (Debian 4.8.1-7+m68k.1) ) #1 Debian 3.10.3-1 (2013-07-27)
> 
> > [    6.720000] bio: create slab <bio-1> at 1
> > [    6.740000] Btrfs loaded
> > [    6.830000] device label ara5-butter devid 1 transid 376178 /dev/nfhd8p3
> > [    7.150000] EXT4-fs (nfhd8p1): mounted filesystem with ordered data mode. Opts: (null)
> > [   14.520000] udevd[228]: starting version 175
> > [   17.820000] device label ara5-butter devid 1 transid 376178 /dev/nfhd8p3
> > [   20.850000] Adding 3670012k swap on /dev/nfhd8p2.  Priority:-1 extents:1 across:3670012k
> > [   21.380000] EXT4-fs (nfhd8p1): re-mounted. Opts: (null)
> > [   31.300000] EXT4-fs (nfhd8p1): re-mounted. Opts: errors=remount-ro
> > [   38.460000] device label ara5-butter devid 1 transid 376178 /dev/nfhd8p3
> > [   38.530000] btrfs: setting nodatacow, compression disabled
> > [   38.540000] btrfs: enabling auto recovery
> > [   38.570000] btrfs: disk space caching is enabled
> > [   38.600000] *** ZERO DIVIDE ***   FORMAT=2
> > [   38.630000] Current process id is 722
> > [   38.660000] BAD KERNEL TRAP: 00000000
> > [   38.680000] Modules linked in: evdev mac_hid ext4 crc16 jbd2 mbcache btrfs xor lzo_compress zlib_deflate raid6_pq crc32c libcrc32c
> > [   38.730000] PC: [<319535b2>] __btrfs_map_block+0x11c/0x119a [btrfs]
> 
> Woops, adding the btrfs devs to CC.
> 

Can you gdb btrfs.ko and do 

list *(__btrfs_map_block+0x11c)

so I can see where this is?  I've not seen this yet, just so I'm clear this is
blowing up because we're doing

blah / 0

right?  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.  Thanks,

Josef

  parent reply	other threads:[~2013-07-30 17:14 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   ` Josef Bacik [this message]
2013-07-30 17:36     ` btrfs zero divide (was: Re: Linux 3.10 problem reports (yes, plural)) 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

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=20130730171329.GF24583@localhost.localdomain \
    --to=jbacik@fusionio.com \
    --cc=debian-68k@lists.debian.org \
    --cc=geert@linux-m68k.org \
    --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).