From: Filipe David Manana <fdmanana@gmail.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: oops BUG unable to handle kernel NULL point dereference IP io_ctl_check_crc
Date: Mon, 11 May 2015 15:03:08 +0100 [thread overview]
Message-ID: <CAL3q7H5bdnOLmHTt_YrUnJb7grmv+UFMSW62e85yK7F9UN24Zg@mail.gmail.com> (raw)
In-Reply-To: <CAJCQCtSXceHtfNYpOekP+8TfiF7WJeHQNwYyNJRYnD0XT2z-XA@mail.gmail.com>
On Sat, May 9, 2015 at 8:43 AM, Chris Murphy <lists@colorremedies.com> wrote:
> On Sat, May 9, 2015 at 12:34 AM, Chris Murphy <lists@colorremedies.com> wrote:
>> https://bugzilla.kernel.org/show_bug.cgi?id=97991
>
> OK it appears to be a 32bit kernel problem, as it happens in an x86_64
> qemu/kvm VM.
>
> But that same vm with the same version 64bit kernel doesn't exhibit the problem.
Sounds like it should have been fixed in rc3 by [1], the same trace
was reported recently [2].
[1] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=1d3c61c2eb3fe4f96d3192212f1bdcee49ea55aa
[2] http://www.spinics.net/lists/linux-btrfs/msg43754.html
>
> --
> Chris Murphy
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Filipe David Manana,
"Reasonable men adapt themselves to the world.
Unreasonable men adapt the world to themselves.
That's why all progress depends on unreasonable men."
next prev parent reply other threads:[~2015-05-11 14:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-09 6:34 oops BUG unable to handle kernel NULL point dereference IP io_ctl_check_crc Chris Murphy
2015-05-09 7:43 ` Chris Murphy
2015-05-11 14:03 ` Filipe David Manana [this message]
2015-05-11 14:16 ` 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=CAL3q7H5bdnOLmHTt_YrUnJb7grmv+UFMSW62e85yK7F9UN24Zg@mail.gmail.com \
--to=fdmanana@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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;
as well as URLs for NNTP newsgroup(s).