linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <clm@fb.com>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: <jbacik@fb.com>, <linux-btrfs@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Dave Jones <davej@redhat.com>
Subject: Re: btrfs: kernel BUG at fs/btrfs/extent_io.c:676!
Date: Tue, 14 Oct 2014 02:31:52 -0400	[thread overview]
Message-ID: <1413268312.2971.1@mail.thefacebook.com> (raw)
In-Reply-To: <543B35D3.6050509@oracle.com>

On Sun, Oct 12, 2014 at 10:15 PM, Sasha Levin <sasha.levin@oracle.com> 
wrote:
> Ping?
> 
> This BUG_ON()ing due to GFP_ATOMIC allocation failure is really silly 
> :(

Agreed, I have a patch for this in testing.  It didn't make my first 
pull but I'll get it fixed up.

-chris



  reply	other threads:[~2014-10-14  6:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-24  1:26 btrfs: kernel BUG at fs/btrfs/extent_io.c:676! Sasha Levin
2014-10-13  2:15 ` Sasha Levin
2014-10-14  6:31   ` Chris Mason [this message]
2015-03-12  2:51     ` Sasha Levin

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=1413268312.2971.1@mail.thefacebook.com \
    --to=clm@fb.com \
    --cc=davej@redhat.com \
    --cc=jbacik@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sasha.levin@oracle.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).