From: Francesco Turco <fturco@fastmail.fm>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: OOM killer and Btrfs
Date: Sun, 04 Sep 2016 12:30:50 +0200 [thread overview]
Message-ID: <1472985050.1817194.715218329.7F4E8977@webmail.messagingengine.com> (raw)
In-Reply-To: <20160904100625.GA305@x4>
On Sun, Sep 4, 2016, at 12:06, Markus Trippelsdorf wrote:
> On 2016.09.04 at 11:59 +0200, Francesco Turco wrote:
> > Is the problem already known? Should I report a bug? Is there a patch I
> > can try? Thanks.
>
> This issue was recently fixed by:
>
> commit 6b4e3181d7bd5ca5ab6f45929e4a5ffa7ab4ab7f
> Author: Michal Hocko <mhocko@suse.com>
> Date: Thu Sep 1 16:14:41 2016 -0700
>
> mm, oom: prevent premature OOM killer invocation for high order
> request
>
> It will be backported to the 4.7.x stable kernel, too.
Great, I will wait for a new 4.7.x release then :)
Thank you for the info!
--
https://www.fturco.net/
prev parent reply other threads:[~2016-09-04 10:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-04 9:59 OOM killer and Btrfs Francesco Turco
2016-09-04 10:06 ` Markus Trippelsdorf
2016-09-04 10:30 ` Francesco Turco [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=1472985050.1817194.715218329.7F4E8977@webmail.messagingengine.com \
--to=fturco@fastmail.fm \
--cc=linux-btrfs@vger.kernel.org \
--cc=markus@trippelsdorf.de \
/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).