Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fusionio.com>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: kernel BUG at mm/page-writeback.c:2317!
Date: Wed, 2 Oct 2013 07:46:05 -0400	[thread overview]
Message-ID: <20131002114605.GB2562@localhost.localdomain> (raw)
In-Reply-To: <20131002170014.60dac0d9@wpkg.org>

On Wed, Oct 02, 2013 at 05:00:14PM +0900, Tomasz Chmielewski wrote:
> Just seen this on a server running 3.12.0-rc3 and btrfs.
> 
> Process writing to btrfs filesystem is stuck.
>

This is probably the bug that Liu Bo just fixed

https://patchwork.kernel.org/patch/2970751/

Thanks,

Josef 

  reply	other threads:[~2013-10-02 11:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-02  8:00 kernel BUG at mm/page-writeback.c:2317! Tomasz Chmielewski
2013-10-02 11:46 ` Josef Bacik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-10-07 22:36 Jan Killius
2013-10-08  1:51 ` Josef Bacik
2013-10-08  2:20 ` Josef Bacik
2013-10-08 15:29   ` Jan Killius

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=20131002114605.GB2562@localhost.localdomain \
    --to=jbacik@fusionio.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mangoo@wpkg.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