linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jérôme Poulin" <jeromepoulin@gmail.com>
To: Josef Bacik <jbacik@fusionio.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Out of memory condition
Date: Tue, 9 Oct 2012 08:34:06 -0400	[thread overview]
Message-ID: <CALJXSJqJrVu2sU=s1_b05AZ4zQqjBMyNeV0s819VKcnCT7YYfA@mail.gmail.com> (raw)
In-Reply-To: <20121005204407.GA12424@localhost.localdomain>

Right now, with the patches applied on 3.5.0, Chrome didn't freeze
under out of memory conditions (2 OOM killer invocation).

On Fri, Oct 5, 2012 at 4:44 PM, Josef Bacik <jbacik@fusionio.com> wrote:
> On Fri, Oct 05, 2012 at 02:23:25PM -0600, Jérôme Poulin wrote:
>> I guess I'll be the guy who will test out of memory conditions! Here's
>> another stack further down the code.
>>
>
> Ok that was just a warning, did the box keep going after that?  I've fixed it up
> and sent a patch, unapply all the patches I've given you and apply the new ones
> I've just sent (there are 3) and see how that works for you.  If you don't get
> any BUG()'s but it's still hung then I'll need sysrq+w to see where you are
> hung, we probably screw up unlocking in these codepaths somewhere.  Thanks,
>
> Josef

      reply	other threads:[~2012-10-09 12:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CALJXSJrtf7wid5xS4H5+E6ws_SjcgjB48ppoU_9+24JSkggKUw@mail.gmail.com>
2012-10-03 14:25 ` Out of memory condition Jérôme Poulin
2012-10-03 20:52   ` Josef Bacik
2012-10-05 17:20     ` Jérôme Poulin
2012-10-05 17:43       ` Josef Bacik
2012-10-05 20:23         ` Jérôme Poulin
2012-10-05 20:44           ` Josef Bacik
2012-10-09 12:34             ` Jérôme Poulin [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='CALJXSJqJrVu2sU=s1_b05AZ4zQqjBMyNeV0s819VKcnCT7YYfA@mail.gmail.com' \
    --to=jeromepoulin@gmail.com \
    --cc=jbacik@fusionio.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).