Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Merlijn Wajer <merlijn@wizzup.org>
To: linux-btrfs@vger.kernel.org
Subject: Linux v4.1-rc1: Unable to handle kernel NULL pointer dereference
Date: Sat, 02 May 2015 18:20:53 +0200	[thread overview]
Message-ID: <5544F965.9040703@wizzup.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 636 bytes --]

Hi,

btrfs fails to work on my rootfs, with a NULL pointer dereference:
http://sprunge.us/aIWe resulting in a panic on boot. This has also been
happening with linux-next-2015042* at least.

It works on 3.8 and 3.18 kernels. The reason the FS is mounted rather
late is because I drop to a shell from inside my initramfs and then
mount it manually to get a trace; the rootfs is encrypted. Initially
mounting the btrfs seems to work, but when actually accessing content it
fails.

My kernel is "dirty" because I applied a single line patch to my device
tree (ARM device): I have no local btrfs changes.

Cheers,
Merlijn


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

                 reply	other threads:[~2015-05-02 16:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5544F965.9040703@wizzup.org \
    --to=merlijn@wizzup.org \
    --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