From: Chris Mason <chris.mason@oracle.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 1/2] stop using highmem for extent_buffers
Date: Wed, 20 Jul 2011 04:00:48 -0400 [thread overview]
Message-ID: <1311148758-sup-6034@shiny> (raw)
In-Reply-To: <4E262ED3.1050609@cn.fujitsu.com>
Excerpts from Li Zefan's message of 2011-07-19 21:26:43 -0400:
> 01:32, Chris Mason wrote:
> > I haven't yet tested this on x86-32, if someone is willing to try this
> > on non-critical test machines I'd appreciate it.
> >
>
> Great work!
>
> I pulled the integration-test branch, and I got this when mounting
> a newly created btrfs:
>
> [ 65.544087] BUG: unable to handle kernel NULL pointer dereference at (null)
> [ 65.544176] IP: [<f98cdc52>] write_extent_buffer+0xad/0xcb [btrfs]
> [ 65.544276] *pde = 00000000
> [ 65.544314] Oops: 0002 [#1] SMP
Ok, so x86-32 isn't working at all ;) I've got a VM I should be able to
reproduce on.
-chris
prev parent reply other threads:[~2011-07-20 8:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 17:32 [PATCH 1/2] stop using highmem for extent_buffers Chris Mason
2011-07-20 1:26 ` Li Zefan
2011-07-20 8:00 ` Chris Mason [this message]
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=1311148758-sup-6034@shiny \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
/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