From: Gustavo Padovan <gustavo@padovan.org>
To: Liu Bo <bo.li.liu@oracle.com>
Cc: chris.mason@fusionio.com, linux-btrfs@vger.kernel.org
Subject: Re: btrfs crash - Null dereference - 3.7.0-rc5-00068-gc5e35d6
Date: Mon, 19 Nov 2012 11:07:52 -0200 [thread overview]
Message-ID: <20121119130752.GA3457@joana> (raw)
In-Reply-To: <20121119103221.GA8810@gmail.com>
Hi Liu,
* Liu Bo <bo.li.liu@oracle.com> [2012-11-19 18:32:23 +0800]:
> On Mon, Nov 19, 2012 at 12:55:40AM -0200, Gustavo Padovan wrote:
> > Hi,
> >
> > my system suddenly crashed and gave me this dump:
> >
> > http://imgur.com/oO6S0
> >
> > I checked and there is not btrfs commit in linus' tree since I compiled this
> > kernel.
> >
>
> Hi Gustavo,
>
> It's weird that NULL pointer oops happens here.
>
> Since you own the kernel, you may also have debuginfo left,
>
> can you please run
> 'gdb fs/btrfs/btrfs.ko' and 'list *block_rsv_release_bytes+0x21' to
> check which one is NULL pointer?
(gdb) list *block_rsv_release_bytes+0x21
0xffffffff811a83c1 is in block_rsv_release_bytes
(fs/btrfs/extent-tree.c:4065).
4060
4061 static void block_rsv_release_bytes(struct btrfs_fs_info *fs_info,
4062 struct btrfs_block_rsv *block_rsv,
4063 struct btrfs_block_rsv *dest, u64
num_bytes)
4064 {
4065 struct btrfs_space_info *space_info = block_rsv->space_info;
4066
4067 spin_lock(&block_rsv->lock);
4068 if (num_bytes == (u64)-1)
4069 num_bytes = block_rsv->size;
(gdb)
Seems block_rsv is NULL here and looking to btrfs_block_rsv_release() it can
only be NULL at this point if global_rsv->full is true otherwise the crash
would happen there. I didn't go any further than this.
Gustavo
next prev parent reply other threads:[~2012-11-19 13:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 2:55 btrfs crash - Null dereference - 3.7.0-rc5-00068-gc5e35d6 Gustavo Padovan
2012-11-19 10:32 ` Liu Bo
2012-11-19 13:07 ` Gustavo Padovan [this message]
2012-11-19 15:27 ` Liu Bo
2012-11-19 16:59 ` Gustavo Padovan
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=20121119130752.GA3457@joana \
--to=gustavo@padovan.org \
--cc=bo.li.liu@oracle.com \
--cc=chris.mason@fusionio.com \
--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 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.