From: Marc Kleine-Budde <mkl@pengutronix.de>
To: bo.li.liu@oracle.com
Cc: linux-btrfs@vger.kernel.org
Subject: Re: NULL pointer dereference in btrfs_async_reclaim_metadata_space
Date: Wed, 25 Jan 2017 16:47:19 +0100 [thread overview]
Message-ID: <0981ebaa-1f22-6586-a450-c0e6f689901e@pengutronix.de> (raw)
In-Reply-To: <20170125154325.GA13419@dhcp-amer-vpn-adc-anyconnect-10-154-187-238.vpn.oracle.com>
[-- Attachment #1.1: Type: text/plain, Size: 1023 bytes --]
On 01/25/2017 04:43 PM, Liu Bo wrote:
> On Wed, Jan 25, 2017 at 10:31:32AM +0100, Marc Kleine-Budde wrote:
>> Hello,
>>
>> I'm using debian's latest 4.9 Kernel on a 32bit armhf SMP board. The
>> filesystem is in raid1 mode using two harddrives. After the system
>> crashed (for yet unknown reason) the mounting of the raid1 failed
>> with the following backtrace:
>
> Since this was happening at mount stage, it seems like our fs_root is
> not set up yet, could you please try this debugging one?
Since this is my production system, I've mounted the FS in the mean time
on an amd64 (debian kernel v4.8.15-2) and it worked without problems.
I'll try to compile a kernel with your patch for the affected systemm
though.
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2017-01-25 15:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 9:31 NULL pointer dereference in btrfs_async_reclaim_metadata_space Marc Kleine-Budde
2017-01-25 15:43 ` Liu Bo
2017-01-25 15:47 ` Marc Kleine-Budde [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=0981ebaa-1f22-6586-a450-c0e6f689901e@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=bo.li.liu@oracle.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 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).