From: Chris Mason <clm@fb.com>
To: <russell@coker.com.au>, <linux-btrfs@vger.kernel.org>
Subject: Re: GPF in 3.13.4 Debian kernel
Date: Sun, 2 Mar 2014 21:35:30 -0500 [thread overview]
Message-ID: <5313EA72.1010000@fb.com> (raw)
In-Reply-To: <201403031123.53133.russell@coker.com.au>
On 03/02/2014 07:23 PM, Russell Coker wrote:
> I've attached the kernel message log from a GPF that occurred running the
> Debian kernel package of kernel 3.13.4. This happens repeatedly and started
> doing so with Debian kernel 3.12.8.
>
> This is not the first time I've seen a filesystem corruption occur related to
> Kmail files that causes a kernel panic. I wonder if Kmail has some file
> access pattern that triggers a BTRFS bug.
>
Looks like this one:
https://git.kernel.org/cgit/linux/kernel/git/mason/linux-btrfs.git/commit/?h=for-linus&id=514ac8ad8793a097c0c9d89202c642479d6dfa34
It's in a batch that needed extra attention for a stable backport, which
I've finally got finished off here.
If you want to try linus master, it should be fixed. Or you can wait
for my weekend run to finish against the stable tree and I'll have it
for you tomorrow.
-chris
next prev parent reply other threads:[~2014-03-03 2:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 0:23 GPF in 3.13.4 Debian kernel Russell Coker
2014-03-03 2:35 ` Chris Mason [this message]
2014-05-01 1:53 ` Russell Coker
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=5313EA72.1010000@fb.com \
--to=clm@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=russell@coker.com.au \
/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).