linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell Coker <russell@coker.com.au>
To: Chris Mason <clm@fb.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: GPF in 3.13.4 Debian kernel
Date: Thu, 01 May 2014 11:53:42 +1000	[thread overview]
Message-ID: <3376675.LutzFkB4bs@xev> (raw)
In-Reply-To: <5313EA72.1010000@fb.com>

On Sun, 2 Mar 2014 21:35:30 Chris Mason wrote:
> 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.

The Debian 3.14.1 kernel fixes this bug.  On a filesystem which gets a GPF on 
a 3.13 kernel 3.14.1 will allow reading the files in question without error.

-- 
My Main Blog         http://etbe.coker.com.au/
My Documents Blog    http://doc.coker.com.au/


      reply	other threads:[~2014-05-01  1:53 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
2014-05-01  1:53   ` Russell Coker [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=3376675.LutzFkB4bs@xev \
    --to=russell@coker.com.au \
    --cc=clm@fb.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).