All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sasha.levin@oracle.com>
To: Chris Mason <clm@fb.com>
Cc: jbacik@fb.com, linux-btrfs@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	Dave Jones <davej@redhat.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	Michal Hocko <mhocko@suse.cz>
Subject: Re: btrfs: kernel BUG at fs/btrfs/extent_io.c:676!
Date: Wed, 11 Mar 2015 22:51:56 -0400	[thread overview]
Message-ID: <5500FF4C.2020702@oracle.com> (raw)
In-Reply-To: <1413268312.2971.1@mail.thefacebook.com>

On 10/14/2014 02:31 AM, Chris Mason wrote:
> 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.

I've re-enabled fs testing after the discussion at LSF/MM (but mostly
due to Michal's patch), and this issue came right back up.

Any updates?


Thanks,
Sasha

WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin <sasha.levin@oracle.com>
To: Chris Mason <clm@fb.com>
Cc: jbacik@fb.com, linux-btrfs@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	Dave Jones <davej@redhat.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	Michal Hocko <mhocko@suse.cz>
Subject: Re: btrfs: kernel BUG at fs/btrfs/extent_io.c:676!
Date: Wed, 11 Mar 2015 22:51:56 -0400	[thread overview]
Message-ID: <5500FF4C.2020702@oracle.com> (raw)
In-Reply-To: <1413268312.2971.1@mail.thefacebook.com>

On 10/14/2014 02:31 AM, Chris Mason wrote:
> 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.

I've re-enabled fs testing after the discussion at LSF/MM (but mostly
due to Michal's patch), and this issue came right back up.

Any updates?


Thanks,
Sasha

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2015-03-12  2:52 UTC|newest]

Thread overview: 5+ 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
2015-03-12  2:51     ` Sasha Levin [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=5500FF4C.2020702@oracle.com \
    --to=sasha.levin@oracle.com \
    --cc=clm@fb.com \
    --cc=davej@redhat.com \
    --cc=jbacik@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.