linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: BUG
Date: Wed, 12 Jun 2013 08:38:25 +0000 (UTC)	[thread overview]
Message-ID: <pan$39a9c$ad4b23f0$bdccf0e6$84b2e405@cox.net> (raw)
In-Reply-To: 51B73E1D.9080902@intellasoft.net

Mark Murawski posted on Tue, 11 Jun 2013 11:11:25 -0400 as excerpted:

> Jun 10 05:24:57 localhost kernel: BUG: unable to handle kernel NULL
> pointer dereference at 0000000000000090

I'll let someone else handle the real technical stuff, but I distinctly 
recall reading that a number of null-pointer bugs had been fixed for 
3.10, and you're running 3.9, so I could suggest trying the latest Linus-
tree rc (3.10.0-rc5 just came out a couple days ago) or live-git HEAD.

I've been running 3.10-pre here with a (new) dual-SSD raid-1 data/
metadata both set of btrfs filesystems (I partition mine down, less eggs 
in one filesystem basket), without issue so far.

Might nor might not be the same bug; as I said I don't get that deep into 
the technical stuff, but it's worth a try.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  reply	other threads:[~2013-06-12  8:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-11 15:11 BUG Mark Murawski
2013-06-12  8:38 ` Duncan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-08-29  2:34 bug lilofile
2013-08-29  2:43 ` bug Liu Bo
2013-08-29 12:25 ` bug David Sterba
2009-07-24 20:28 Bug Steven Pratt
2009-07-24 20:29 ` Bug Chris Mason

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='pan$39a9c$ad4b23f0$bdccf0e6$84b2e405@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --cc=linux-btrfs@vger.kernel.org \
    /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).